/*
Theme Name: Syncify
Theme URI: https://syncify.se
Author: Syncify
Description: Theme for syncify.se. Built on Syncify Design System v.1. Hybrid theme: classic PHP templates plus theme.json, ACF Blocks and block patterns.
Version: 0.1.0
Requires at least: 6.5
Requires PHP: 8.2
License: Proprietary
Text Domain: syncify
*/

/*
  WHAT IS IN THIS FILE, IN ORDER

  The banners below are the ones written through the file. Search for the
  name to jump to one. No line numbers: they go stale on the first edit and
  then mislead.

    Tokens theme.json cannot express   signal colour, hairlines, radii,
                                       durations, field and header
                                       measurements
    The reduced motion contract        why 100% of every keyframe is the
                                       rest state
    Layout layer                       container, gutter, rhythm tokens,
                                       skip link
    The page is as tall as the page    the canvas painted in the footer's
                                       colour under a short page
    Primitives layer                   image, picture ratio, link and
                                       button, focus. The rules every
                                       component inherits
    Header                             sticky nav, admin bar offset, the
                                       scroll-padding every anchor needs
    Over the hero                      the header's scroll driven swap on
                                       the front page
    Over the ground                    the same swap on every other page
    The menu's second level            the dropdown panel, .has-js and
                                       .is-nav-enhanced
    The narrow header                  the toggle and the full screen panel
    Fat menu                           the full width panel under the header
    The content column                 the 1080 column, the bands that
                                       break out of it, the running measure
    Footer                             dark surface, link columns, fine print
    The footer columns as accordions   the toggles on a phone
    Section layer                      section padding, dark and surface
                                       variants
    Hero                               full height dark band. Also carries
                                       buttons, .lead and .display, which
                                       have no banner of their own
    Section label                      the small uppercase section marker
    Mechanism diagram                  the figure and its caption
    Columns                            plain text columns under the diagram
    Ownership                          two bounded surfaces and a line
    Fields                             input, textarea, select, search form
    Partner band                       gliding logotype row and its edge fade
    Flow row                           snapping horizontal card scroller
    Contact                            light closing section, the ribbon
                                       rising out of the footer
    Chip                               small label, and the outlined status chip
    Media card                         square picture with a metadata row
    Trust section                      items under hairlines, icon beside title
    Contact page                       two columns, ways to reach us, form slots,
                                       the grid of systems
    The logotypes the slots hold       [syncify_logo] marks, .logo-missing
    Security page                      band head, check groups,
                                       split rows, statement
    About page                         mirrored panels, picture frames,
                                       the logotype grid
    The service provider's details     the company fold and its list
    Process page                       the status colours, feature columns,
                                       the direction rows, system lists
    Panels                             the white card and its rows, the
                                       transaction log's steps
    Integrationer page              tall hero, specification rows,
                                       connector cards, ruled lists
    ERP migration page                 the bordered card grid, the cards,
                                       the hero diagram
    The editor's flow margin           grid cells that must not take the
                                       group block's margin
    The dash that travels along a path the flow diagram's moving dash
    Reconciliation page                the card grid on dark, the system
                                       cells
    Integration page                   the pair of marks, the narrow
                                       container
    Integration pair                   the benefit columns, the flow band
    Integration hub                    the system page's bands, the
                                       "Skapa ett flow" dialog
    Order to cash page                 the dark band that is not a hero,
                                       the direction rows
    Transaction log                    the process page's hero panel
    Partner page                       the step list beside the track
    Policy page                        the contents list beside the text
    Platform page                      the wide fan diagram, the case row
    The flow on its end                the pattern diagrams below 720px
    Article                            heading, date, picture, text
    The article list                   the posts page, rows under hairlines
    Career page                        the application grid, its ribbon
                                       and its card
    The integration pair               the integrationer page's hero
                                       illustration

  Two things live deliberately outside this file. The palette, the type
  scale and the spacing scale are in theme.json. Per block styling is in
  assets/css/blocks/, one file per block, loaded only when the block is on
  the page.
*/

/*
  Tokens theme.json cannot express.

  The signal colour deliberately does NOT live in theme.json's palette. A
  palette entry becomes selectable as a background and text colour in the
  block editor, and the design system is unambiguous: cyan is carried only
  by data that moves or deviates, never by buttons, links, headings, icons,
  surfaces, hover states or decoration. It therefore lives here, where only
  the diagram components reach it.
*/
:root {
  --signal-flow: #00B2E2;

  --hairline: 1px;
  --hairline-color-dark: #3B4750;

  /* The two corner radii. Buttons, fields and small controls take the
     first, panels, cards and frames the second. */
  --radius-button: 8px;
  --radius-card: 14px;

  /* Four more steps of the design system's graphite scale, used by the
     hero's mood layer and nowhere else. They are named rather than written
     as loose hex so the next person can see they belong to a scale, and
     they are here rather than in theme.json's palette because an editor
     should not be offered nine shades of the same grey in a colour picker. */
  --graphite-800: #1F2A33;
  --graphite-600: #33434F;
  --graphite-500: #3F5563;
  --graphite-400: #56707F;

  /* Muted text on the dark surface: the footer's tagline, its column
     headings and its fine print. Graphite 200 in the design system.

     It lives here and not in theme.json's palette for the same reason the
     signal colour does: a palette entry becomes selectable as a text and
     background colour in the block editor, and this one is footer chrome,
     not a choice an editor should be offered. Measured at 6.00:1 on
     graphite deep, so it clears 4.5:1 as body text. */
  --text-muted-on-dark: #8EA3B0;

  /* The header's own height. Read by the sticky offset and by the
     scroll-padding every anchor target needs because of it. */
  --header-height: 72px;

  --field-height: 48px;
  --field-pad-x: 14px;
  --field-gap: 12px;
  --field-label-gap: 8px;
  /* A field on a dark band, from the design system: lifted off the ground
     rather than white on it, with a line that still clears 3:1. */
  --field-fill-on-dark: rgba(255, 255, 255, .08);
  --field-line-on-dark: rgba(255, 255, 255, .45);

  --ease: cubic-bezier(.4, 0, .2, 1);
  --dur-hover: 200ms;
  /* A surface changing state, such as the header going solid. Slower than
     a hover so the change reads as the page moving, not as a flicker. */
  --dur-surface: 250ms;
  /* The design system's hover-lift and hover-zoom. Where they apply is
     under "HOVER LIFTS A CARD". */
  --hover-lift: translateY(-3px);
  --hover-zoom: scale(1.03);
}

/* ------------------------------------------------------------------
   The reduced motion contract.

   animation-timeline is the line that matters. A scroll driven animation
   IGNORES animation-duration, so shortening the duration does nothing to
   it: without this the reader who asked for no motion gets the animation
   pinned at its starting frame instead of its finished one. Disconnecting
   the timeline hands the animation back to time, where the duration and
   the fill mode can reach it.

   Then forwards locks every element on its 100% frame.

   THE AUTHORING RULE THAT FOLLOWS, and it is not optional:

     100% must be the rest state.

   Write the finished line, the solid header, the arrived element as the
   END of the keyframes, never the beginning. Reverse it and the reader
   who opted out of motion gets a line that never arrives.

   Firefox has no scroll driven animations at all, so it lands on the same
   frame by the same rule. Degradation and reduced motion are one state,
   which means one thing to check rather than two.
   ------------------------------------------------------------------ */
@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-timeline: none !important;
    animation-duration: .01ms !important;
    animation-iteration-count: 1 !important;
    animation-fill-mode: forwards !important;
    transition-duration: .01ms !important;
    scroll-behavior: auto !important;
  }
}

/* ------------------------------------------------------------------
   Layout layer.

   theme.json sets colour, type and scale. This is the minimum needed to
   give the page edges, and nothing more: a fluid gutter of 20 to 48px,
   everything left aligned, and columns separated by 1px hairlines.

   The maximum width is 1700px [Emilie 20 okt], against v.1's 1440. It is
   the box, gutters included, so the content itself stops at 1604. Every
   width cap and edge calculation reads this token; the figure also stands
   in theme.json's wideSize and in inc/partner-band.php's min_width.
   ------------------------------------------------------------------ */

:root {
  --container-max: 1700px;
  --gutter: clamp(20px, 4vw, 48px);
  /* THE GROUND OUTSIDE THE CONTENT COLUMN [Emilie 8 okt].

     Several page regions are not capped at --container-max: the front page's
     and the band pages' main runs to the window, and the bands inside it do
     too, while .container inside them stops at --container-max and centres.
     Past that every one of those bands grows and the column does not.

     The decorative figures were placed from the band's right edge, so on a
     wide window, or on any window a reader has zoomed out of, they walked
     away from the words and stood alone against the glass. Measured on the
     contact page at 1600: the column ended at 1520 and the figure stood at
     1536 to 1600.

     This is the distance between the two edges, and it is zero until the
     window is wider than the column. A figure that adds it keeps its place
     relative to the words at every width. The percentage is resolved where
     the token is used, which is against the band each figure sits in.

     Written once because six figures need it. Two more, .section--tall and
     the integration hero, had already solved it by hand with the same
     arithmetic and a floor of their own; those two are left alone rather
     than rewritten, because a floor is not what this token expresses. */
  --outside-container: max(0px, calc((100% - var(--container-max)) / 2));
  /* Line length for running text. [proposal] v.1 states no figure. */
  --text-measure: 68ch;

  /* Rhythm. Every vertical distance between bands comes from one of these
     three, so a component never invents its own. A local exception is how
     the rhythm stops being readable. */
  --section-pad: clamp(64px, 8vw, 112px);
  --section-pad-hero: clamp(88px, 12vw, 176px);
  --block-gap: var(--wp--preset--spacing--80);
  /* v.1's --stack-lg: the distance from a band's heading block down to the
     grid or figure under it. */
  --stack-lg: clamp(48px, 6vw, 88px);

  /* The fixed steps are theme.json's spacing presets, v.1's 4 to 80 plus 96
     and 144. 20, 40 and 80 came last and carry the in-between slugs 45, 65
     and 85, because the older slugs are stored in post_content and must
     keep their values. theme.json sets defaultSpacingSizes to false: left
     on, WordPress's own scale took slugs 20 to 80 and spacing--60 measured
     36px, not 32 (read in the page's global styles, 16 nov). */
}

/* Width includes border and padding. Without this the container becomes
   --container-max plus two gutters, and the measure is wrong. */
*, *::before, *::after {
  box-sizing: border-box;
}

/* ACF'S OWN WRAPPER AROUND INNER BLOCKS HAS NO BOX.

   From ACF block version 2 upwards the plugin wraps whatever <InnerBlocks />
   produced in a div of its own on the front end. ACF 6.2 registered these
   blocks as version 1 and so emitted nothing; 6.8 on WordPress 7.1 registers
   them as 3 and emits seven of these on the front page alone.

   It is a level the theme's CSS did not know about and it broke the flow
   row: .flow-row is a flex container, the wrapper became its only child, and
   the five cards stopped being flex items and stacked.

   display: contents removes the box and leaves the children where the
   stylesheet expects them. It is what the wrapper is for: none of the three
   templates gives <InnerBlocks /> a class, so nothing is meant to be drawn
   on it. IF ONE EVER DOES, that wrapper wants a box again and this rule has
   to stop covering it. */
.acf-innerblocks-container {
  display: contents;
}

/* THE hidden ATTRIBUTE HAS TO OUTRANK THE THEME'S OWN DISPLAY, and without
   this it does not. The browser's own [hidden] { display: none } is a user
   agent rule, and ANY author rule that sets display beats it however plain
   the selector is.

   Two controls are rendered hidden and revealed by script, so that a page
   without JavaScript never shows a control that cannot control: the
   navigation's toggle and the flow row's head. The first was safe because
   it starts at display: none and is switched on by a class the script
   adds. The second was not: .flow-head is flex, so it was drawn, greyed
   and inert, with scripting off.

   THE ATTRIBUTE IS DOUBLED ON PURPOSE, which is the same device
   .band-head.band-head uses further down: it lifts this to two selectors'
   worth of specificity so it wins over a component's own class wherever that
   component sits in the file, and it needs no !important to do it. */
[hidden][hidden] {
  display: none;
}

/* ------------------------------------------------------------------
   The page is as tall as the page, and the window is filled under it.

   THE PAGE IS NOT STRETCHED TO THE WINDOW [Emilie 8 okt]. A short page, or
   any page seen zoomed out, is shorter than the screen, and something has
   to stand between the last word and the bottom edge. Stretching main puts
   that space INSIDE the page, as white under a dark band or as a field of
   empty band: 891px between the last word and the footer on the contact
   page at 1600 by 2400.

   SO THE PAGE STOPS WHERE IT STOPS. The footer follows the content
   immediately, at every window size, and what fills the rest of the screen
   is the canvas behind the document, painted in the footer's own colour.
   A reader sees the footer run to the bottom edge; there is no gap to
   measure because the gap is not in the page.

   THE COLOUR IS ON html, NOT ON body, and the two are not interchangeable.
   A background on body alone propagates to the canvas and would paint the
   whole window dark behind a white page. With html carrying one, body keeps
   its own box and paints the page's white only as far as the page goes.
   body's background comes from theme.json, which is where the palette is.

   body is still a column flex so the three regions stack predictably, and
   flex rather than a three row grid because body does not reliably have
   three children: WordPress injects the admin bar, plugins inject their own
   markup, and a fixed row template breaks the moment something else
   arrives.
   ------------------------------------------------------------------ */
html {
  background: var(--wp--preset--color--graphite-deep);
}
body {
  display: flex;
  flex-direction: column;
}

/* No growth. The region is exactly as tall as the bands in it, which is
   what keeps the footer against the content. */
.site-main {
  flex: 0 0 auto;
}
.site-header,
.site-footer {
  flex: none;
}

/* ------------------------------------------------------------------
   Primitives layer.

   The rules every component inherits instead of solving again. Nothing
   here is about one section or one block. The half that cannot be
   expressed in CSS, the shape of editor-authored HTML, lives in
   inc/primitives.php.
   ------------------------------------------------------------------ */

/* PRIMITIVE: image.

   width and height are always set on the element, because the attributes
   are what reserve the space and stop the page shifting while images
   load. Once they are set, the image will not scale with its column
   unless height is released, which is what these two lines do. Without
   them a wide logo overflows its card and a narrow one is stretched.

   Inline SVG is excluded on purpose: icons are sized explicitly by
   syncify_icon() and must not be rescaled by their container. */
img, video {
  max-width: 100%;
  height: auto;
}

/* PRIMITIVE: picture ratio, offered on the image block as a style.

   .media-frame below does the same job for a box that has no picture in
   it yet. This cannot reuse it: a style lands on the block's <figure>,
   which may also carry a caption, and .media-frame clips and proportions
   everything inside it. So the ratio goes on the picture and the caption
   stays outside both.

   The radius is not repeated here. theme.json already rounds core/image.

   Registered in inc/block-styles.php. */
.wp-block-image:is(.is-style-frame-wide, .is-style-frame-square, .is-style-frame-portrait) img {
  width: 100%;
  aspect-ratio: var(--ratio);
  object-fit: cover;
}
.wp-block-image.is-style-frame-wide { --ratio: 16 / 7; }
.wp-block-image.is-style-frame-square { --ratio: 1; }
.wp-block-image.is-style-frame-portrait { --ratio: 4 / 5; }

/* PRIMITIVE: link and button.

   A link navigates, a button acts. That decision belongs to the markup,
   so both are styled from the same class and look identical: choosing
   the right element must never cost a visual difference, or templates
   will choose by appearance instead.

   The element reset is here because a button does not inherit font or
   colour on its own. */
button.button {
  font: inherit;
  cursor: pointer;
  appearance: none;
}

/* PRIMITIVE: the hand on a list and a file picker [Emilie 30 okt].

   A select and a file input are clicked like buttons, but the browser
   gives them the arrow. Every form on the site, the theme's own and
   Gravity Forms', gets the hand from this one rule, by the element and
   not by a plugin class. The file input's button is a part of its own
   and needs saying twice. A disabled control keeps the arrow. */
select:not(:disabled),
input[type="file"]:not(:disabled),
input[type="file"]:not(:disabled)::file-selector-button {
  cursor: pointer;
}

/* Hidden from the eye, not from a screen reader. For the text that names a
   control whose visible label is a glyph. Not .skip-link: that one is a
   component with its own focus behaviour, and borrowing it here would make
   this text appear when the control takes focus. */
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* Words a line must not break inside, written around them in the text.
   "e-post" broke after its hyphen at 375 [Emilie 16 nov]. Not the
   non-breaking hyphen U+2011: the self-hosted Poppins has no glyph for it,
   measured in Chrome, and the browser drew it in the fallback font. */
.no-wrap {
  white-space: nowrap;
}

/* PRIMITIVE: focus and keyboard.

   One rule for everything focusable, never redefined per component. The
   colour is v.1's focus-ring [19 okt]: graphite 300 on a light ground,
   graphite 200 on a dark one. Measured: #5B7A8C 4.36:1 on the ground, #8EA3B0
   6.0:1 on graphite deep and 4.8:1 on graphite.

   NOT currentColor, which it was. That is the control's own ink, and the
   ring is drawn outside the control: on the filled button the ink is
   white, so the ring was white on the white page and could not be seen.

   A SURFACE THAT CHANGES THE GROUND CHANGES THE TOKEN. The dark ones are
   listed here; the header over the hero sets it in its keyframes, and the
   two white menu panels inside that header set it back. A new dark
   surface goes in this list, unless it is dark at one width only: the
   header without the script is, and sets the token where it turns
   graphite, under 956. */
:root {
  --focus-ring: var(--wp--preset--color--graphic);
}
.site-footer,
.section--dark,
.section--graphite,
.section--graphite-deep,
.section--hero,
.is-nav-open .site-header {
  --focus-ring: var(--text-muted-on-dark);
}
:where(a, button, input, select, textarea, summary, [tabindex]):focus-visible {
  outline: 2px solid var(--focus-ring);
  outline-offset: 2px;
}

/* The container. Everything that belongs in the column gets this, including
   inside a full-bleed band such as the footer. */
.container {
  max-width: var(--container-max);
  margin-inline: auto;
  padding-inline: var(--gutter);
}

/* Narrower text column. Keeps the container's left edge: sections must all
   start on the same pixel, only the line length is shortened. */
.container--narrow > :is(h2, h3, p, ul, ol, .buttons),
.is-style-container-narrow > :is(h2, h3, p, ul, ol, .buttons) {
  max-width: 68ch;
}

/* Skip link. Invisible until it takes keyboard focus. */
.skip-link {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}
.skip-link:focus {
  position: static;
  width: auto;
  height: auto;
  margin: 0;
  padding: var(--wp--preset--spacing--30) var(--gutter);
  overflow: visible;
  clip-path: none;
  display: block;
}

/* ------------------------------------------------------------------
   Header.

   The design system's Nav: 72px tall, sticky at the top, logotype left,
   links pushed right, outline CTA last.

   Solid is the rest state everywhere: the page ground, opaque, with a
   hairline under it. OPAQUE AND NOT A PERCENTAGE: a partly transparent
   ground lets whatever scrolls under it show through as faint letters
   rather than as a wash, and v.1 has no blur to make that readable.

   Two scroll driven variants fade INTO it from a bare header at the top of
   the page, and both are below: over-hero, which also carries white ink
   over the dark hero, and over-ground, which is every other template and
   changes nothing but the surface.

   On a wide window the menu's second level opens as a dropdown panel, or
   as a fat menu where inc/mega-menu.php builds one; below 956 the whole
   navigation becomes a full screen panel behind a toggle.
   ------------------------------------------------------------------ */
.site-header {
  position: sticky;
  top: 0;
  z-index: 20;
  min-height: var(--header-height);
  background: var(--wp--preset--color--ground);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
  color: var(--wp--preset--color--text-strong);
  transition:
    background var(--dur-surface) var(--ease),
    color var(--dur-surface) var(--ease),
    border-color var(--dur-surface) var(--ease);
}
.site-header__inner {
  display: flex;
  align-items: center;
  gap: var(--wp--preset--spacing--60);
  /* One pixel short of the token so the header, border included, comes to
     exactly the token. At the full token the header was 73px, and the hero
     that pulls up under it by the token left a 1px strip of white body
     showing through the transparent header. */
  min-height: calc(var(--header-height) - 1px);
  max-width: var(--container-max);
  margin-inline: auto;
  padding-inline: var(--gutter);
}

/* The admin bar is fixed at the very top with a z-index far above this one,
   so a header pinned to 0 slides underneath it and looks like it stopped
   working. Only logged in editors see this, which is exactly the people who
   look at the site while building it.

   The bar's own heights, from WordPress: 32px on desktop, 46px on tablet,
   and below 600px it stops being fixed and scrolls away, so the offset goes
   back to zero. */
.admin-bar .site-header {
  top: 32px;
}
@media (max-width: 782px) {
  .admin-bar .site-header {
    top: 46px;
  }
}
@media (max-width: 600px) {
  .admin-bar .site-header {
    top: 0;
  }
}

/* A pinned header covers whatever the page scrolls to. The scroll port
   therefore reserves the header's height plus a little air, so "Se hur
   flödet blir spårbart" lands on the heading and not under it, and so a
   link or field reached with Tab is scrolled clear of the header instead
   of under it (WCAG 2.4.11). On the root and not as a scroll-margin on
   every [id]: a margin only reaches anchor targets, never what focus
   scrolls to, and the two together would add up to twice the offset. */
html {
  scroll-padding-top: calc(var(--header-height) + var(--wp--preset--spacing--50));
}

/* ------------------------------------------------------------------
   Over the hero. [decision 22 Sep, reversing 21 Sep]

   On the front page the header starts transparent with white ink and
   becomes the solid surface as the hero leaves the window. A scroll
   timeline, not a script: it runs on the compositor and does no work per
   frame.

   The rule above stays the rest state and stays solid. Everything about
   the transparent half lives in the keyframes below, so a browser without
   scroll driven animations, and a reader who asked for no motion, both
   get the solid header. There is no state that puts white ink on a white
   surface. Firefox is the browser without it today; it lands on solid.

   The swap runs over the last 48px before the white sheet reaches the
   header and finishes 40px early. Early is the safe side: a solid header
   over the last strip of hero is readable, a transparent one over the
   first strip of sheet is not.

   IT IS A STEP AND NOT A FADE, 5 okt. White ink needs a dark surface and
   dark ink needs a light one, so interpolating both across the same range
   walks them through a middle where neither works. Measured over the old
   keyframes: under 4.5:1 for 60 per cent of the range, about 29px of
   scrolling, bottoming at 1.11:1 where a half white surface met a half
   grey ink. No curve avoids it, because the two requirements cross. The
   surface, the ink, the rule and the logotype therefore change at the same
   instant, halfway through the range, which leaves two states and both
   read: white on the hero at 15.73:1, graphite on the ground at 11.99:1.

   The 100% frame repeats the rest state on purpose. The animation must
   end exactly where the base rule already is, or the header would jump
   the moment the range ended.
   ------------------------------------------------------------------ */
@keyframes syncify-header-solidify {
  0%, 50% {
    background: transparent;
    border-bottom-color: transparent;
    color: var(--wp--preset--color--text-on-dark);
    --focus-ring: var(--text-muted-on-dark);
  }
  50.01%, 100% {
    background: var(--wp--preset--color--ground);
    border-bottom-color: var(--wp--preset--color--hairline);
    color: var(--wp--preset--color--text-strong);
    --focus-ring: var(--wp--preset--color--graphic);
  }
}
/* The two marks change with the surface, or the light one would be half
   visible on white. */
@keyframes syncify-logo-to-dark {
  0%, 50%      { opacity: 0; }
  50.01%, 100% { opacity: 1; }
}
@keyframes syncify-logo-to-light {
  0%, 50%      { opacity: 1; }
  50.01%, 100% { opacity: 0; }
}

@supports (animation-timeline: scroll()) {
  .site-header--over-hero {
    animation: syncify-header-solidify auto linear both;
    animation-timeline: scroll();
    animation-range:
      calc(100svh - var(--header-height) - 88px)
      calc(100svh - var(--header-height) - 40px);
  }
  .site-header--over-hero .site-logo__mark--dark {
    animation: syncify-logo-to-dark auto linear both;
    animation-timeline: scroll();
    animation-range:
      calc(100svh - var(--header-height) - 88px)
      calc(100svh - var(--header-height) - 40px);
  }
  .site-header--over-hero .site-logo__mark--light {
    animation: syncify-logo-to-light auto linear both;
    animation-timeline: scroll();
    animation-range:
      calc(100svh - var(--header-height) - 88px)
      calc(100svh - var(--header-height) - 40px);
  }
}

/* ------------------------------------------------------------------
   Over the ground.

   The same swap on every template that is not the front page: no surface
   at the very top of the page, the solid surface from the first stretch of
   scrolling. Same machinery as over the hero, and the same rest state, so
   this adds no third state to reason about.

   ONE DIFFERENCE, AND IT IS THE POINT. What is behind the header here is
   the page's own white surface, not a dark picture, so the ink stays dark
   and the logotype stays the dark mark. Only the surface and its hairline
   fade in. The hero variant swaps ink and mark because it has to;
   doing it here would put white ink on white.

   The range is short, 48px, and starts at the very top: the header is bare
   only while the page has not moved. It is the same 48 the hero variant
   swaps over, so the two feel like one behaviour rather than two.

   The border keeps its box and loses only its colour, so nothing below the
   header moves when the state changes.

   The 100% frame repeats the rest state, for the same reason as above: the
   animation has to end exactly where the base rule already is. Reduced
   motion and Firefox both land on that frame, which is the solid header. */
@keyframes syncify-header-ground-solidify {
  from {
    background: transparent;
    border-bottom-color: transparent;
  }
  to {
    background: var(--wp--preset--color--ground);
    border-bottom-color: var(--wp--preset--color--hairline);
  }
}

@supports (animation-timeline: scroll()) {
  .site-header--over-ground {
    animation: syncify-header-ground-solidify auto linear both;
    animation-timeline: scroll();
    animation-range: 0 48px;
  }
}

/* ------------------------------------------------------------------
   Over a dark opening band. [Emilie 6 nov]

   A bands page whose first section is dark has its band pulled up under
   the header, and the header carries white ink and the light mark over
   it at the top. Before this the header sat bare over the light ground
   above the band, which read as a white header, and faded in over the
   first 48px, which left a grey strip where a half white surface met the
   dark.

   SAME 48px AS OVER-GROUND, so every page but the front page has one
   rhythm, but over-hero's keyframes: a step at 24px and not a fade, for
   the reason given there. Not bare until the band leaves, as the front
   page is: that hero is sticky and stands still, these bands scroll, and
   their own words would pass under a transparent header (measured 6 nov,
   the security page's last line under the logotype at 390).

   THE CONDITION DECIDES, NOT THE TEMPLATE. Six pages open dark today and
   any later one that opens on .section--dark or .section--hero gets this
   without a flag.

   Inside the same @supports as over-ground, the pull up included: without
   scroll timelines the header is the solid rest state, and the band stays
   below it as before.

   The pull is --header-pull, read by the hero tiers further down so the
   band keeps its height below the header and its words where they were. */
@supports (animation-timeline: scroll()) {
  .site-main--bands > section:first-child:is(.section--dark, .section--hero) {
    --header-pull: var(--header-height);
    margin-top: calc(var(--header-pull) * -1);
    padding-top: calc(var(--section-pad) + var(--header-pull));
  }
  :root:has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header--over-ground {
    animation-name: syncify-header-solidify;
  }
  :root:has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header--over-ground .site-logo__mark--dark {
    animation: syncify-logo-to-dark auto linear both;
    animation-timeline: scroll();
    animation-range: 0 48px;
  }
  :root:has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header--over-ground .site-logo__mark--light {
    animation: syncify-logo-to-light auto linear both;
    animation-timeline: scroll();
    animation-range: 0 48px;
  }
}

/* position relative because the two marks are stacked: the light one is
   absolute inside this box. */
.site-logo {
  position: relative;
  display: flex;
  align-items: center;
  flex: none;
  color: inherit;
}
/* The mark is sized by its context, not by this rule: the header wants it
   read at a glance beside the navigation, the footer wants it as the sender's
   signature at the foot of the page, and those are not the same size.

   Height only. The file is 557 by 211, and width auto lets the aspect ratio
   do the arithmetic rather than a second number that can drift out of step
   with this one.

   Both figures are taken from the design system's 26px: the header 40
   [Emilie 20 okt, up from a fifth above it], the footer twice it. Written
   against that baseline rather than against each other, so neither drifts
   when the other is adjusted. The header's 40 still sits inside its 72px
   row; past about 64 the mark would push the header taller. */
.site-logo__mark {
  display: block;
  width: auto;
  height: var(--logo-height, 26px);
}
/* Both marks are in the DOM and stacked. The dark one showing is the rest
   state; the light one is faded in over the hero by the scroll timeline
   above and while the panel is open. An opacity change, never a request. */
.site-logo__mark--light {
  position: absolute;
  inset: 0;
  opacity: 0;
}
/* Set on the mark itself, not on .site-header and .site-footer. Those two
   already have their own blocks elsewhere in this file, and a second one
   here, a hundred lines away, is how a rule gets edited without anyone
   noticing the other half. */
.site-header .site-logo__mark {
  --logo-height: 40px;
}
.site-footer__brand .site-logo__mark {
  --logo-height: 52px;
}
/* The footer's link to the start page [Emilie 29 okt]. Inline, because
   the brand cell is a plain block: as a flex box the link would run the
   cell's full width and take clicks beside the mark. */
.site-footer__brand .site-logo {
  display: inline-flex;
}

/* THE LIST AND THE BUTTON SIT ON ONE ROW. The button is inside this
   element so it reaches the panel on a phone; see syncify_header_cta(). On
   the row it is the second flex child, and the gap matches
   .site-header__inner's so it stands where it would as a sibling. */
.site-nav {
  margin-inline-start: auto;
  display: flex;
  align-items: center;
  gap: var(--wp--preset--spacing--60);
}
/* The panel's own header row, built by nav.js. The row only has a place
   in the narrow panel; see "The panel" under max-width 955px. */
.site-nav__home {
  display: none;
}
.site-nav__list {
  display: flex;
  flex-wrap: wrap;
  /* 36 is the design's. It needs 982px of window, and the row is wanted
     from 956, so between those widths the gap is the thing that gives.
     Below 1100 rather than at 982 exactly, so the change is not a jump
     the eye catches at one width. */
  gap: clamp(26px, 36px - (1100px - 100vw) * 0.07, 36px);
  margin: 0;
  padding: 0;
  list-style: none;
  font-size: var(--wp--preset--font-size--brod-liten);
  font-weight: 500;
}
.site-nav__list a {
  padding-bottom: 2px;
  color: inherit;
  text-decoration: none;
  border-bottom: 1px solid transparent;
}
/* The current page is marked by a line, not by colour: colour alone is
   not enough to carry a state. Everything else steps back slightly. */
.site-nav__list .current-menu-item > a,
.site-nav__list .current_page_item > a {
  border-bottom-color: currentColor;
}
.site-nav__list a:hover {
  border-bottom-color: currentColor;
}

/* ------------------------------------------------------------------
   The menu's second level.

   Four things belong on this row and eleven pages have to be reachable
   from it, so four of the four carry the rest. The parent is still a link
   to its own page; the toggle beside it is a separate control, the same
   division the footer's columns use.

   WITHOUT THE SCRIPT the sub list is simply visible. It is not the design
   at this width, but every link works, which is the trade the footer makes
   too.

   TWO CLASSES CARRY THAT, AND THEY MEAN DIFFERENT THINGS.

   .has-js is written on <html> by an inline snippet in the head, before
   the first paint, and says only that scripting is on. What hangs on it is
   what the final state looks like with nothing open: the sub lists folded
   away, the panel shut, the hamburger on screen. None of it needs a button
   to exist yet, and all of it used to arrive one paint late, as a list
   that flashed up and vanished.

   .is-nav-enhanced is written by nav.js on its last line and says the
   script got all the way through. What hangs on it is everything that
   needs the controls nav.js builds. A script that threw halfway therefore
   leaves its own work hidden, and the head snippet puts .has-js back at
   DOMContentLoaded when nav.js never reported in, so the open version
   stands exactly as before.
   ------------------------------------------------------------------ */
.site-nav__list > li {
  position: relative;
  display: flex;
  align-items: center;
  gap: var(--wp--preset--spacing--10);
  flex-wrap: wrap;
}
.site-nav .sub-menu {
  display: flex;
  flex-direction: column;
  gap: 10px;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* The toggle. Hidden until the script is there to make it do something,
   for the same reason the flow row hides its step buttons. */
.nav-more {
  display: none;
  align-items: center;
  justify-content: center;
  width: 28px;
  height: 28px;
  padding: 0;
  border: 0;
  background: none;
  color: inherit;
  cursor: pointer;
}
.is-nav-enhanced .nav-more {
  display: inline-flex;
}

/* A chevron, drawn rather than fetched, like the footer's plus. Two
   borders on a square turned 45 degrees; it turns the other way when the
   panel opens, so the mark says which way the list goes. */
.nav-more__mark {
  display: block;
  width: 7px;
  height: 7px;
  margin-top: -3px;
  border-right: 1.5px solid currentColor;
  border-bottom: 1.5px solid currentColor;
  transform: rotate(45deg);
  transition: transform var(--dur-surface) var(--ease);
}
.nav-more[aria-expanded="true"] .nav-more__mark {
  margin-top: 3px;
  transform: rotate(-135deg);
}

/* Enhanced: the list is a panel that opens under its parent. Folded away
   from .has-js, opened by a button that only exists under the other
   class, which is why the two selectors differ. */
.has-js .site-nav .sub-menu {
  display: none;
}
.is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] ~ .sub-menu {
  display: flex;
  position: absolute;
  top: calc(100% + 18px);
  inset-inline-start: 0;
  z-index: 1;
  min-width: max(220px, 100%);
  /* THE PANEL'S INSET IS SMALL AND THE ROOM IS ON THE ROWS, because each
     row is a filled block now and has to run the panel's full width. The
     8px that is left keeps a fill off the border and its radius. */
  padding: var(--wp--preset--spacing--20);
  gap: 2px;
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  /* OPAQUE, and with its own ink. Over the hero the header's colour is
     white and .site-nav__list a inherits it, which on a white panel is
     nothing at all. The panel states both rather than inheriting one.
     The focus ring too, for the same reason. */
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
  --focus-ring: var(--wp--preset--color--graphic);
}
/* THE DROPDOWN IS A DESKTOP THING, and these rules have to say so. The
   hamburger panel below 956 holds the same .sub-menu markup on a dark
   ground, and an unscoped fill and ink would land there too: graphite on
   graphite, and the row ink dark on dark.

   956 IS THE PAIR OF THE 955 FURTHER DOWN, where the panel takes over.
   Move one and move the other. */
@media (min-width: 956px) {
  /* A ROW IN THE DROPDOWN IS A BLOCK, NOT AN UNDERLINE [Emilie 7 okt].

     The row above it is still marked with a line, and should be: those items
     sit on the page's own ground with nothing behind them, and a fill there
     would be a button where there is none. Inside the panel there IS a
     surface to fill, and a line under one word in a list of four reads as an
     afterthought.

     THE LINE HAS TO BE TURNED OFF EXPLICITLY. It comes from
     .site-nav__list a, which these links are inside, so the dropdown
     inherits both the transparent border and the rules that colour it.

     DESKTOP ONLY. The hamburger panel's own sub menu is styled inside the
     max-width: 955px block further down and keeps its dividing lines; this
     rule set sits outside that block, where the dropdown lives.

     STATE IS NOT CARRIED BY COLOUR ALONE. WordPress writes aria-current on
     the current item, checked in the markup, so the fill is what the eye
     gets and the attribute is what everything else gets. That is what the
     note on the row above is about, and it still holds. */
  .is-nav-enhanced .site-nav .sub-menu a {
    display: block;
    white-space: nowrap;
    padding: 10px var(--wp--preset--spacing--30);
    border-bottom: 0;
    border-radius: var(--radius-button);
    color: var(--wp--preset--color--text-strong);
  }
  /* Hover is the greyer of the two, because it is a maybe: the pointer is
     over the row and nothing has happened yet.

     HAIRLINE AND NOT SURFACE, measured. Surface is the paler grey and
     came to 1.06:1 against the panel it sits on, which is a state the
     eye does not catch. Hairline is 1.28:1 and reads, and the row ink on
     it is still 9.30:1. */
  .is-nav-enhanced .site-nav .sub-menu a:hover,
  .is-nav-enhanced .site-nav .sub-menu a:focus-visible {
    background: var(--wp--preset--color--hairline);
    border-bottom: 0;
  }
  /* The page you are on is the stronger of the two, and takes the ink with
     it: graphite on the ground is 11.99:1, and the ground on graphite is the
     same number the other way round. */
  .is-nav-enhanced .site-nav .sub-menu .current-menu-item > a,
  .is-nav-enhanced .site-nav .sub-menu .current_page_item > a,
  .is-nav-enhanced .site-nav .sub-menu a[aria-current="page"] {
    background: var(--wp--preset--color--graphite);
    color: var(--wp--preset--color--text-on-dark);
    border-bottom: 0;
  }
}

/* The CTA borrows the header's ink so it follows the swap with everything
   else. Scoped to the header: .button--outline sets colour further down and
   a bare .site-header__cta would tie with it and lose on source order. */
.site-header .site-header__cta {
  flex: none;
  white-space: nowrap;
  color: inherit;
  border-color: currentColor;
}
.site-header .site-header__cta:hover {
  background: color-mix(in srgb, currentColor 12%, transparent);
  border-color: currentColor;
}

/* ------------------------------------------------------------------
   The narrow header: a toggle and a full screen panel.

   Below 956 the navigation stops being a row and becomes a panel that
   covers the window, opened from a button in the header.

   PROGRESSIVE, NOT CONDITIONAL. The panel is only hidden once the head
   snippet has written .has-js on <html>, and that snippet takes the class
   back off when nav.js never reports in. Without scripting the button
   stays hidden and the navigation stays a plain visible list, which is
   longer but works. Nothing is ever behind a button that cannot be
   pressed.
   ------------------------------------------------------------------ */
.nav-toggle {
  display: none;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  margin-inline-start: auto;
  padding: 0;
  border: 0;
  background: none;
  color: inherit;
  cursor: pointer;
}

/* Two bars, drawn rather than fetched. The third is the ::after on the
   first, so the whole mark is one element to animate. */
.nav-toggle__bars,
.nav-toggle__bars::before,
.nav-toggle__bars::after {
  display: block;
  width: 24px;
  height: 2px;
  background: currentColor;
  transition: transform var(--dur-hover) var(--ease), opacity var(--dur-hover) var(--ease);
}
.nav-toggle__bars::before,
.nav-toggle__bars::after {
  content: "";
  position: relative;
}
.nav-toggle__bars::before {
  top: -8px;
}
.nav-toggle__bars::after {
  top: 6px;
}

/* Open: the bars become a cross. The middle bar goes, the outer two
   rotate onto each other. */
[aria-expanded="true"] .nav-toggle__bars {
  background: transparent;
}
[aria-expanded="true"] .nav-toggle__bars::before {
  top: 2px;
  transform: rotate(45deg);
}
[aria-expanded="true"] .nav-toggle__bars::after {
  top: 0;
  transform: rotate(-45deg);
}

/* THE HAMBURGER TAKES OVER BEFORE THE LINKS WRAP, not at a round number.
   A row that wraps grows the header from 72 to 90.

   THE FULL ROW IS WANTED FROM 956 [Emilie 6 okt], so the panel ends at
   955. At the design's 36px between links the row needs 982, so the gap
   is tightened below 1100; see .site-nav__list further up. The menu is
   built in wp-admin and a longer label eats the slack: if it wraps again,
   the two numbers to change are here and there. */
@media (max-width: 955px) {
  .site-header__inner {
    gap: var(--wp--preset--spacing--40);
  }

  /* THE CTA IS IN THE PANEL, NOT HIDDEN `[12 okt]`. A customer with an
     account has to reach the portal from a phone.

     It is inside the nav element, so it arrives in the panel on its
     own. The panel is a flex column, which puts it last, under the links,
     and stretches it to the full width: a target the thumb can find
     without aiming. The space above it separates it from the navigation,
     because it is not one of the links. */
  /* stretch, not the row's centre. The row centres its two children on the
     cross axis, which in a column is the horizontal one, so inherited it
     left the button at its own 123px in the middle of the panel. */
  .site-nav {
    align-items: stretch;
    gap: clamp(24px, 6vw, 40px);
  }

  /* AT THE FOOT OF THE PANEL, AND IT STAYS THERE `[Emilie 12 okt]`.
     margin-top:auto eats whatever height is left over, so the button sits
     on the bottom edge at any window height and moves with it as the
     window is dragged. When the links are tall enough to fill the panel
     the margin resolves to nothing and the button simply follows them,
     inside the panel's own scroll. Measured at 1200, 760, 560 and 420
     tall: on the bottom edge in each, and still last in the scroll when
     the links no longer fit.

     THE HEADER'S OWN BUTTON [Emilie 12 okt]: white outline and white
     words on the panel's dark ground, as it stands over the hero on a
     wide screen. White on graphite deep is 15.73:1.

     Written out as text-on-dark rather than left to inherit, because the
     header's ink is dark on light pages and the panel is dark on all of
     them. Hover is the wide header's too: a 12 per cent wash of the ink
     behind the words. Focus matches hover, so a reader on a keyboard is
     shown the same thing as a reader with a mouse. */
  .site-header .site-header__cta {
    justify-content: center;
    margin-top: auto;
    /* LOWER THAN A LINK'S ROW [Emilie 12 okt]. At the row's full height,
       70px at 390, it reads as a slab. The words keep the links' size; the
       height comes from a tighter line and its own padding, 56px at 390.
       Still above the 44px touch minimum at every width. */
    padding-block: var(--wp--preset--spacing--30);
    line-height: 1.25;
    background: transparent;
    border-color: var(--wp--preset--color--text-on-dark);
    color: var(--wp--preset--color--text-on-dark);
  }
  .site-header .site-header__cta:hover,
  .site-header .site-header__cta:focus-visible {
    background: color-mix(in srgb, var(--wp--preset--color--text-on-dark) 12%, transparent);
  }

  /* WITHOUT THE SCRIPT, THE HERO HEADER NEEDS A GROUND OF ITS OWN
     [8 okt, measured at 320].

     The note under "The menu's second level" says the trade without the
     script is that the sub list stands open: not the design, but every
     link works. At this width that was not true. The whole menu unfolds
     into the header, which grows from 72 to 304px, and over the hero the
     header is transparent with light ink. The top 240px of it therefore
     sit on the page's own white, and the first six links measured
     1.00:1 against it: white on white, present in the DOM and invisible
     on the screen.

     The panel's own ground, so the links read as the panel they would be
     if the script had run. White on graphite deep is 15.73:1.

     ONLY WITHOUT THE SCRIPT and only over the hero. Every other header at
     this width already has dark ink on the page's white.

     animation: none IS WHAT MAKES THE BACKGROUND TAKE. The transparency is
     not a declaration here, it is the first keyframe of
     syncify-header-solidify, which runs on the scroll timeline with
     fill both. An animated value beats an ordinary one in the cascade, so
     a background on its own changed nothing: measured, still 1.00:1. The
     animation is what is turned off, and then the ground applies.

     The solidify effect is not missed in this state: the header is a 304px
     block of links rather than a 72px bar, and it has to be opaque at
     every scroll position, not only past the hero. */
  html:not(.has-js) .site-header--over-hero,
  html:not(.has-js):has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header--over-ground {
    animation: none;
    background: var(--wp--preset--color--graphite-deep);
    border-bottom-color: var(--hairline-color-dark);
    color: var(--wp--preset--color--text-on-dark);
    --focus-ring: var(--text-muted-on-dark);
  }

  /* The hamburger is on screen as soon as the head says scripting is on.
     It is also what nav.js measures to decide whether it is in panel mode,
     so this declaration is the breakpoint; see isPanel() in nav.js. */
  .has-js .nav-toggle {
    display: inline-flex;
  }

  /* The panel. Over the header's own row and everything below it.

     THE WHOLE MENU SLIDES IN, HEADER ROW INCLUDED [Emilie 22 okt]. The
     panel starts at the header's top, not under it, and carries its own
     row in the header's place: .site-nav__home, the white mark, built by
     nav.js. The header itself does not change when the panel opens; it is
     covered. Only the close button stands above the panel, because it is
     the one control both share. */
  .is-nav-enhanced .site-nav {
    position: fixed;
    inset: 0;
    z-index: 19;
    display: flex;
    flex-direction: column;
    margin: 0;
    padding: 0 var(--gutter) clamp(24px, 6vw, 48px);
    overflow-y: auto;
    overscroll-behavior: contain;
    background: var(--wp--preset--color--graphite-deep);
    color: var(--wp--preset--color--text-on-dark);
  }
  /* No admin bar rule here on purpose. The panel's top and its row's
     height are set by nav.js from the header's measured edges (top and
     --nav-head), on open and on resize, which covers the admin bar at
     every one of its heights, the header's own border, and a wrapped row.
     A second value in CSS would fight it. */

  /* The panel's header row: the mark where the header's mark is, on the
     panel's graphite. Sticky, so the links scroll under it and never under
     the close button beside it. */
  .is-nav-enhanced .site-nav__home {
    position: sticky;
    top: 0;
    z-index: 1;
    display: flex;
    flex: none;
    align-items: center;
    height: var(--nav-head, var(--header-height));
    /* The links start where they started when the panel began under the
       header: the panel's old top padding, less the column gap the row
       now stands in front of (.site-nav's, under max-width 955px). */
    margin: 0 calc(-1 * var(--gutter)) calc(clamp(24px, 6vw, 48px) - clamp(24px, 6vw, 40px));
    padding-inline: var(--gutter);
    background: inherit;
  }
  .is-nav-enhanced .site-nav__home a {
    display: block;
  }
  /* The header mark's height, from .site-header .site-logo__mark. */
  .is-nav-enhanced .site-nav__home img {
    display: block;
    width: auto;
    height: 40px;
  }

  /* THE CLOSE BUTTON TURNS WHITE AS THE PANEL REACHES IT, not before. It
     stands above the panel near the right edge, so the panel's edge passes
     behind it about 60ms into the 320ms slide, and leaves it again about
     200ms into the slide out. Measured from the curve at 375px; the
     button sits further right on a wider window, so the moment comes a
     little earlier on the way in and later on the way out. A step, not a
     fade: it is one colour or the other behind it.

     Only while the panel moves. A delay on the button at rest would make
     it lag the header's own ink swap on scroll; .is-nav-closing is on the
     header for the length of the slide out. */
  .is-nav-enhanced .nav-toggle {
    position: relative;
    z-index: 20;
  }
  .site-header.is-nav-open .nav-toggle {
    color: var(--wp--preset--color--text-on-dark);
    transition: color 0s linear 60ms;
  }
  .site-header.is-nav-closing .nav-toggle {
    transition: color 0s linear 200ms;
  }

  /* Closed. hidden rather than a transform, so nothing inside can take
     focus or be read while the panel is shut. */
  .is-nav-enhanced .site-nav[hidden] {
    display: none;
  }

  /* IT SLIDES IN FROM THE RIGHT AND OUT TO THE RIGHT [Emilie 22 okt].
     The transform only moves a panel that is already shown: nav.js takes
     hidden off, lets one frame pass with the panel off to the right, then
     adds .is-shown. Closing runs the other way, and hidden goes back on
     when the slide has ended. So shut is still hidden, as above, and the
     slide is only the way between. */
  .is-nav-enhanced .site-nav {
    transform: translateX(100%);
    transition: transform 320ms var(--ease);
  }
  .is-nav-enhanced .site-nav.is-shown {
    transform: none;
  }

  /* THE WHITE MARK DOES NOT TRAVEL WITH THE PANEL [Emilie 22 okt]. It
     stands still on the header's black mark, and the panel's edge uncovers
     it: where the panel has reached, the mark is white; where it has not,
     the black one shows. As the edge crosses, the white mark seems to
     slide over the black one.

     The row moves the opposite way to the panel, the same distance on the
     same curve, so the two cancel and the row stays put on screen. The
     row is as wide as the panel, so -100% of it is the panel's 100%. The
     panel clips what lies outside it (overflow), and that clip is the
     moving edge. */
  .is-nav-enhanced .site-nav__home {
    transform: translateX(-100%);
    transition: transform 320ms var(--ease);
  }
  .is-nav-enhanced .site-nav.is-shown .site-nav__home {
    transform: none;
  }

  @media (prefers-reduced-motion: reduce) {
    .is-nav-enhanced .site-nav,
    .is-nav-enhanced .site-nav__home {
      transition: none;
    }
  }

  /* Shut before the script got here too, or the panel's whole content
     stands in the header for as long as the deferred file takes to
     arrive, which is the flash this pair of classes exists to remove.
     The attribute above takes the job over from nav.js, and the handover
     happens inside one task: applyWidth() writes hidden, and only then
     does the class go on. */
  .has-js:not(.is-nav-enhanced) .site-nav {
    display: none;
  }

  /* THE PANEL'S ROW, IN ONE PLACE `[12 okt]`. The links' padding and size,
     and the size Mitt Syncify takes at the foot. The button does not share
     the row's height; see its rule earlier in this block. */
  .is-nav-enhanced .site-nav {
    --nav-row-pad: clamp(16px, 4vw, 24px);
    --nav-row-font: clamp(1.5rem, 4vw + 0.5rem, 2rem);
  }
  .is-nav-enhanced .site-nav__list {
    flex-direction: column;
    gap: 0;
    font-size: var(--nav-row-font);
    font-weight: 400;
  }
  /* Mitt Syncify at the size of the links above it [Emilie 12 okt].
     .button--sm's brod-liten reads as a footnote under display type. */
  .is-nav-enhanced .site-header__cta {
    font-size: var(--nav-row-font);
  }
  .is-nav-enhanced .site-nav__list a {
    display: block;
    padding-block: var(--nav-row-pad);
    border-bottom: 0;
  }
  /* THE TOP LEVEL IS A BLOCK TOO [Emilie 7 okt], on the same reading as
     the sub menu: hover is the lifted grey, the page you are on inverts.
     The numbers are the panel's, measured against graphite deep: the
     hover fill stands 1.65:1 off it with white ink at 9.53:1, and the
     current row is the ground at 11.99:1 and 15.07:1 off the panel.

     NO LINES BETWEEN THE TOP LEVEL ITEMS [Emilie 22 okt]. There were
     hairlines on the li, kept on the reading that they were the list's
     only structure at rest. The panel goes without them now: the rows'
     padding and display type separate them, as the filled rows already
     do in the sub menu.

     THE ROW WITH A CHEVRON FILLS AS ONE ROW, chevron included [Emilie
     13 nov]. Hovering either the word or the chevron fills both, so the
     row reads as one item, and both open the sub menu. */
  .is-nav-enhanced .site-nav__list > li > a {
    /* 16px INSIDE THE FILL [Emilie 19 okt], so the words do not touch the
       edge of the current row's white block. */
    padding-inline: var(--wp--preset--spacing--40);
    border-radius: var(--radius-button);
  }
  /* 8px BEFORE THE CHEVRON [Emilie 13 nov]. The chevron's 44px box already
     holds the row's right edge. The row is 335 wide at 375, which leaves
     a label 335 - 16 - 8 - 44 = 267px, and 212px at 320; Integrationer is
     155. A longer label puts the chevron on a line of its own. */
  .is-nav-enhanced .site-nav__list > li:has(> .nav-more) > a {
    padding-right: var(--wp--preset--spacing--20);
    border-radius: 8px 0 0 8px;
  }
  .is-nav-enhanced .site-nav__list > li > .nav-more {
    border-radius: 0 8px 8px 0;
  }
  /* ONE FOCUS RING AROUND THE ROW [Emilie 13 nov]. The word and the
     chevron both open the sub menu here (nav.js), so the ring says one
     control whichever of the two holds focus. The link draws it, over
     its own box and the chevron's 44px. */
  .is-nav-enhanced .site-nav__list > li:has(> .nav-more) > a {
    position: relative;
  }
  .is-nav-enhanced .site-nav__list > li:has(> .nav-more) > a::after {
    content: "";
    position: absolute;
    inset: 0 -44px 0 0;
    border-radius: var(--radius-button);
    pointer-events: none;
  }
  .is-nav-enhanced .site-nav__list > li:has(> .nav-more) > :is(a, .nav-more):focus-visible {
    outline: none;
  }
  .is-nav-enhanced .site-nav__list > li:has(> a:focus-visible, > .nav-more:focus-visible) > a::after {
    outline: 2px solid var(--focus-ring);
    outline-offset: 2px;
  }
  /* The current row is left out of the row selector: it outweighs the
     current row's rule below, and put the grey fill under its dark text,
     too little contrast [Emilie 13 nov]. The current row stays inverted
     on hover. */
  .is-nav-enhanced .site-nav__list > li > a:hover,
  .is-nav-enhanced .site-nav__list > li > a:focus-visible,
  .is-nav-enhanced .site-nav__list > li:not(.current-menu-item, .current_page_item, :has(> a[aria-current="page"])):has(> a:hover, > .nav-more:hover, > a:focus-visible, > .nav-more:focus-visible) > :is(a, .nav-more) {
    background: var(--hairline-color-dark);
  }
  /* The current row inverts as one row too, or its white block would stop
     square against an unfilled chevron. */
  .is-nav-enhanced .site-nav__list > .current-menu-item > :is(a, .nav-more),
  .is-nav-enhanced .site-nav__list > .current_page_item > :is(a, .nav-more),
  .is-nav-enhanced .site-nav__list > li > a[aria-current="page"],
  .is-nav-enhanced .site-nav__list > li:has(> a[aria-current="page"]) > .nav-more {
    background: var(--wp--preset--color--ground);
    color: var(--wp--preset--color--text-strong);
  }

  /* The second level inside the full screen panel. Not a floating panel
     here: there is nothing to float over, the surface is already dark,
     and a white card inside it would read as a different site. It opens
     in place, indented, and takes the row to full width. */
  .is-nav-enhanced .site-nav__list > li {
    flex-wrap: wrap;
    /* The link and the chevron touch, so the row's fill has no seam. */
    column-gap: 0;
  }
  .is-nav-enhanced .site-nav__list > li > a {
    flex: 1;
  }
  /* The chevron takes the link's height, so the fill is one block. */
  .is-nav-enhanced .site-nav .nav-more {
    width: 44px;
    height: auto;
    min-height: 44px;
    align-self: stretch;
  }
  /* THE CHEVRON AT THE CLOSE MARK'S SIZE [Emilie 12 okt]. The cross is two
     24px bars turned 45 degrees, so it spans 17px with a 2px line. A 12px
     square turned the same way spans 17px too, and the border matches the
     bars. The 7px mark is the wide header's, beside 14px words. */
  .is-nav-enhanced .site-nav .nav-more__mark {
    width: 12px;
    height: 12px;
    margin-top: -6px;
    border-width: 2px;
  }
  .is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] .nav-more__mark {
    margin-top: 6px;
  }
  .is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] ~ .sub-menu {
    position: static;
    width: 100%;
    min-width: 0;
    margin: 0 0 clamp(16px, 4vw, 24px);
    padding: 0 0 0 var(--wp--preset--spacing--40);
    border: 0;
    border-radius: 0;
    background: none;
    color: inherit;
    --focus-ring: inherit;
    font-size: var(--wp--preset--font-size--ingress);
  }
  /* THE SAME BLOCK AS THE DROPDOWN, read against this panel instead
     [Emilie 7 okt]. A filled row needs the panel's whole width, so the
     16px that indented the sub menu moves into the row: the fill runs
     edge to edge in the content column and the words stay stepped in,
     which is what the indent was for.

     THE LINES BETWEEN THE SUB LINKS GO WITH IT. They divided rows that
     had nothing else to divide them; a filled row divides itself. The
     line under the open parent is gone too [Emilie 22 okt], with the
     other top level lines. */
  .is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] ~ .sub-menu {
    /* The indent moves to the row, so it has to be taken off here. Same
       selector as the rule above that set it, because that one carries an
       attribute and a plainer one loses to it. */
    padding-left: 0;
  }
  .is-nav-enhanced .site-nav .sub-menu a {
    /* THE FILL STEPS IN WITH THE WORDS [Emilie 22 okt]. The sub link's
       hover and current fill starts 16px in from the top level's, and the
       words sit 16px inside it, as they do in the top level row: so the
       words are where they were, 32px in, and the fill's left edge marks
       the second level. The right edge still runs to the end of the row. */
    margin-left: var(--wp--preset--spacing--40);
    padding: 10px var(--wp--preset--spacing--40);
    border-radius: var(--radius-button);
    white-space: normal;
  }
  /* Measured against this panel's own ground, graphite deep #1B242C, and
     not against the white one the dropdown sits on.

     HOVER IS hairline-dark, the dark twin of the grey the dropdown uses:
     1.65:1 against the panel, so the row reads as touched, and the white
     ink on it is 9.53:1. graphite was the other candidate and came to
     1.26:1, which is not a state. */
  .is-nav-enhanced .site-nav .sub-menu a:hover,
  .is-nav-enhanced .site-nav .sub-menu a:focus-visible {
    background: var(--hairline-color-dark);
  }
  /* The current page inverts, which is the dropdown's rule read on a dark
     ground: there the fill is graphite and the ink white, here the fill is
     the off white ground and the ink graphite. 11.99:1 either way, and
     the block itself stands 15.07:1 off the panel. */
  .is-nav-enhanced .site-nav .sub-menu .current-menu-item > a,
  .is-nav-enhanced .site-nav .sub-menu .current_page_item > a,
  .is-nav-enhanced .site-nav .sub-menu a[aria-current="page"] {
    background: var(--wp--preset--color--ground);
    color: var(--wp--preset--color--text-strong);
  }

  /* THE HEADER DOES NOT CHANGE WHEN THE PANEL OPENS [Emilie 22 okt]. It
     used to turn graphite at once, white mark and a hairline under it,
     while the panel was still on its way in. Now the panel covers it,
     header row included, so there is nothing to swap and no line under it.

     NO BLUR on .site-header. v.1 has none, and it would also break the
     panel: like filter, backdrop-filter makes its element the containing
     block for every position: fixed descendant, and this panel is a
     descendant of the header. Inset 0 is then measured against the 72px
     header and the panel comes out 72px tall with a scrollbar. */
}

/* The page behind the panel does not scroll.

   On html ONLY. Not on body, and the reason is measured, not stylistic:
   overflow hidden turns body into a scroll container, and position:
   sticky fastens to the nearest scrolling ancestor. The header then stops
   following the window and follows body, which is not scrolled, so with
   the page 1500px down the header measured at -1500 to -1427, the panel
   took its top from that, and the reader saw an empty graphite panel
   with every link above the top of the screen. html alone is the root
   scroller: locking it stops the page and leaves the header where it was. */
html.is-nav-open {
  overflow: hidden;
}

/* ------------------------------------------------------------------
   Fat menu `[14 okt]`.

   What a top level item opens when the menu gives it a third level; see
   inc/mega-menu.php. On a wide screen a full width panel under the header:
   introduction, one column per child with hairlines between, the latest
   article in a card. In the hamburger panel it opens in place like the
   dropdown does, and only the columns come along: the introduction says
   what the top level row already says, and the card is news, not
   navigation.

   Shut and opened by the same two classes and the same button as the
   dropdown, under "The menu's second level" above. Without the script
   it stands open in the flow, which is that section's trade too.
   ------------------------------------------------------------------ */
.has-js .site-nav .mega-menu {
  display: none;
}
.mega-menu__columns,
.mega-menu__links {
  margin: 0;
  padding: 0;
  list-style: none;
}
/* The row's underline rule reaches in here through .site-nav__list a.
   The panel marks hover and the current page its own way in each width
   below, so nothing of the row's rule is kept. */
.site-nav .mega-menu a {
  display: block;
  padding-bottom: 0;
  border-bottom: 0;
}

@media (min-width: 956px) {
  /* The page you are on is underlined on the title alone, so the
     description under it is not. Hover is a fill, below, so the two states
     never look alike. */
  .mega-menu__title {
    border-bottom: 1px solid transparent;
  }
  .mega-menu a[aria-current="page"] .mega-menu__title {
    border-bottom-color: currentColor;
  }

  /* The panel spans the header, so its item must not be the box it is
     placed against. The header is sticky, and sticky is a containing
     block, so the panel hangs from the header's bottom edge.

     ONE HAIRLINE BELOW 100% `[Emilie 14 okt]`. An absolute box is placed
     from its containing block's padding edge, which is inside the border,
     so at 100% the panel covered the header's hairline and the two menus
     ran together with nothing between them. */
  .site-nav__list > .menu-item-has-mega {
    position: static;
  }
  .is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] ~ .mega-menu {
    display: block;
    position: absolute;
    top: calc(100% + var(--hairline));
    inset-inline: 0;
    z-index: 1;
    max-height: calc(100svh - var(--header-height));
    overflow-y: auto;
    /* A LINE AND A SHADOW AT THE FOOT `[Emilie 14 okt]`. Over a page
       that is white under the panel too, the hairline alone was not
       enough to say the panel lies on top of it. The shadow is the
       cards' own two layers, the same graphite at the same strengths,
       so the theme has one shadow and not two. */
    border-bottom: 1px solid var(--wp--preset--color--hairline);
    box-shadow:
      0 1px 2px color-mix(in srgb, var(--wp--preset--color--graphite) 5%, transparent),
      0 10px 24px -6px color-mix(in srgb, var(--wp--preset--color--graphite) 9%, transparent);
    /* Opaque and with its own ink and focus ring, for the dropdown's
       reason: over the hero the header's ink is white. */
    background: var(--wp--preset--color--ground);
    color: var(--wp--preset--color--text-strong);
    --focus-ring: var(--wp--preset--color--graphic);
    font-weight: 400;
  }
  /* The parent link keeps the row's line while its panel is open, so the
     row says which item the panel belongs to. Hover and the current page
     already draw it through .site-nav__list a. */
  .is-nav-enhanced .site-nav__list > li > a:has(+ .nav-more[aria-expanded="true"] ~ .mega-menu) {
    border-bottom-color: currentColor;
  }
  /* AN OPEN PANEL MAKES THE HEADER SOLID, at any scroll position. A white
     panel hung under a transparent header over the hero reads as two
     things. The scroll swap is an animation, and an animated value beats
     a declared one, so the animation is what is turned off; the values
     are the rest state the swap ends on.

     WITHOUT THE SCRIPT EVERY PANEL IS OPEN, in the flow and on the
     page's own ground, so the same rule holds with no button to ask.
     Before it the header kept its white ink over the hero and over a
     dark opening band, and the panels read white on #FAFAFA.

     The dark band's condition is written out again because its own
     animations, under "Over a dark opening band", carry it and outweigh
     the short selector; without it the light mark stayed on the ground,
     with the script as well as without it [Emilie 6 nov]. */
  .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu),
  .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu) .site-logo__mark,
  :root:has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu),
  :root:has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu) .site-logo__mark,
  html:not(.has-js) .site-header:has(.mega-menu),
  html:not(.has-js) .site-header:has(.mega-menu) .site-logo__mark,
  html:not(.has-js):has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header:has(.mega-menu),
  html:not(.has-js):has(.site-main--bands > section:first-child:is(.section--dark, .section--hero)) .site-header:has(.mega-menu) .site-logo__mark {
    animation: none;
  }
  .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu),
  html:not(.has-js) .site-header:has(.mega-menu) {
    background: var(--wp--preset--color--ground);
    border-bottom-color: var(--wp--preset--color--hairline);
    color: var(--wp--preset--color--text-strong);
  }
  .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu) .site-logo__mark--dark,
  html:not(.has-js) .site-header:has(.mega-menu) .site-logo__mark--dark {
    opacity: 1;
  }
  .site-header:has(.nav-more[aria-expanded="true"] ~ .mega-menu) .site-logo__mark--light,
  html:not(.has-js) .site-header:has(.mega-menu) .site-logo__mark--light {
    opacity: 0;
  }

  /* The panel's content takes the header's own measure, so the
     introduction starts under the logotype.

     THREE TRACKS, AND THE LINKS SIT AGAINST THE CARD `[Emilie 14 okt]`.
     The free room goes between the introduction and the columns, so the
     introduction stands alone and the destinations read as one group. The
     last column's own padding is the gap to the card.

     A GRID AND NOT A FLEX ROW. In a flex row, where the room goes is
     decided by auto margins and by how three items shrink against each
     other, and in one browser it landed between the columns and the card.
     Here it is stated: the middle track takes it and the columns stand at
     its end.

     The card's track is auto, so with no article it is nothing wide and
     the columns stand against the panel's right edge instead. */
  .mega-menu__inner {
    display: grid;
    /* The introduction gives way on a narrow window rather than the
       columns: at 960 a fixed 300 left them 166 wide. The middle track
       is never narrower than its longest word, so it is the introduction
       that shrinks there, never the columns running into the card. */
    grid-template-columns: minmax(0, clamp(220px, 24vw, 300px)) minmax(min-content, 1fr) auto;
    align-items: start;
    max-width: var(--container-max);
    margin-inline: auto;
    padding: var(--wp--preset--spacing--65) var(--gutter);
  }
  .mega-menu__intro {
    padding-inline-end: var(--wp--preset--spacing--60);
  }
  .mega-menu__columns {
    display: flex;
    justify-self: end;
    max-width: 100%;
  }
  /* A set width, not a share of the room: one link under a label is still
     a column as wide as the others. Shrinks when the window does, but
     never under its longest word: at 0, Integrationsplattform runs out of
     its column at every width under 1430 once Use cases takes two
     columns. */
  .mega-menu__column {
    flex: 0 1 280px;
    min-width: min-content;
    padding-inline: var(--wp--preset--spacing--60);
  }
  /* Lines between columns only. The introduction has the free room to set
     it apart, and a line there as well was one divider too many. */
  .mega-menu__column + .mega-menu__column {
    border-inline-start: 1px solid var(--wp--preset--color--hairline);
  }
  .mega-menu__card {
    width: clamp(220px, 22vw, 290px);
    position: relative;
    padding: 28px;
    border-radius: var(--radius-card);
    background: var(--wp--preset--color--surface);
    transition: background var(--dur-hover) var(--ease);
  }
  /* THE WHOLE CARD IS THE LINK `[Emilie 14 okt]`, and Läs mer is still the
     only link in it. Its ::after is stretched over the card, so a pointer
     anywhere on it follows the article, while a screen reader meets one
     link with one name. Wrapping the card in an a would read the title,
     the text and Läs mer out as one long link name. */
  .mega-menu__card .mega-menu__more::after {
    content: "";
    position: absolute;
    inset: 0;
    border-radius: inherit;
  }
  /* The rows' hover fill, so the card answers the pointer the same way. */
  .mega-menu__card:hover {
    background: color-mix(in srgb, var(--wp--preset--color--surface), var(--wp--preset--color--hairline) 40%);
  }

  .mega-menu .section-label {
    margin-bottom: var(--wp--preset--spacing--45);
  }
  /* The 12px the first row pads with makes up the rest, so the title
     stands 20px under the label like the introduction's heading does. */
  .mega-menu .mega-menu__label {
    margin-bottom: var(--wp--preset--spacing--20);
  }
  .mega-menu__heading {
    margin: 0 0 var(--wp--preset--spacing--45);
    font-size: var(--wp--preset--font-size--rubrik-1);
    font-weight: 300;
    line-height: 1.25;
  }
  .mega-menu__card-title {
    margin: 0 0 var(--wp--preset--spacing--40);
    font-size: var(--wp--preset--font-size--ingress);
    line-height: 1.3;
  }
  .mega-menu__lead {
    margin: 0 0 var(--wp--preset--spacing--45);
    color: var(--wp--preset--color--text-body);
    font-size: var(--wp--preset--font-size--brod-liten);
    line-height: 1.7;
  }
  /* a. in the selector to outweigh .site-nav .mega-menu a, which takes
     every other link in the panel off the row's underline. */
  .site-nav .mega-menu a.mega-menu__more {
    display: inline;
    border-bottom: 1px solid currentColor;
    font-weight: 500;
  }

  /* A ROW IS A BLOCK THAT FILLS ON HOVER `[Emilie 14 okt]`. The padding
     is taken back by the negative margin, so the words stay on the column
     label's edge and only the fill reaches past it. The gap shrinks by the
     padding it gained, which keeps the rows where they stood.

     THE DROPDOWN'S TWO STATES `[Emilie 14 okt]`: hairline on hover,
     graphite with white ink on the page you are on, so a sub menu reads
     the same whichever kind it is. Measured on this panel: hairline is
     1.34:1 against it and carries the title at 9.31:1.

     THE DESCRIPTION CHANGES INK WITH THE ROW. text-body on hairline is
     4.25:1, under 4.5, so on hover it takes the title's ink. On graphite
     it takes --text-muted-on-dark, 4.78:1, and the title white, 12.52:1. */
  .mega-menu__links {
    display: flex;
    flex-direction: column;
    gap: var(--wp--preset--spacing--10);
  }
  .site-nav .mega-menu__links a {
    margin-inline: -14px;
    padding: var(--wp--preset--spacing--30) 14px;
    border-radius: var(--radius-button);
    font-size: var(--wp--preset--font-size--brod);
    font-weight: 500;
    transition: background var(--dur-hover) var(--ease);
  }
  .site-nav .mega-menu__links a:hover,
  .site-nav .mega-menu__links a:focus-visible {
    background: var(--wp--preset--color--hairline);
  }
  .site-nav .mega-menu__links a:hover .mega-menu__desc,
  .site-nav .mega-menu__links a:focus-visible .mega-menu__desc {
    color: var(--wp--preset--color--text-strong);
  }
  /* Written after hover with the same weight, so the page you are on stays
     graphite under the pointer. */
  .site-nav .mega-menu__links a[aria-current="page"] {
    background: var(--wp--preset--color--graphite);
    color: var(--wp--preset--color--text-on-dark);
  }
  /* Not text-muted-on-dark: that is measured on graphite deep, and on
     graphite it falls to 4.8:1, which read as too faint under a white
     title. Three quarters white over graphite is 7.8:1 and still a step
     below the title's 12.5:1. */
  .site-nav .mega-menu__links a[aria-current="page"] .mega-menu__desc {
    color: color-mix(in srgb, var(--wp--preset--color--text-on-dark) 75%, var(--wp--preset--color--graphite));
  }

  /* TWO LINKS TO A COLUMN `[Emilie 14 okt]`, so the panel is as tall as
     two rows and not as tall as the longest list. Any list with a third
     link wraps into a second column beside the first, read top to bottom
     and then across; Plattformen, with two, is untouched. The condition
     is the count and not the column's name, so a list that grows in
     wp-admin follows on its own.

     FROM 1280 ONLY. Under that the double column shrank toward 110px a
     link and every description broke on each word, so a narrower window
     keeps the single list and the extra height. Between 1280 and 1430
     some titles take two lines; the panel is still lower than with one
     list, and every word stays inside its column.

     32 between the columns: each fill reaches 14 past its words, so two
     fills side by side keep 4px apart.

     A COLUMN IS NEVER NARROWER THAN ITS LONGEST WORD `[17 nov]`. At
     minmax(0, 1fr) the five links under Use cases made three columns in
     350px at 1280, and avstämning and AI-projekt ran into the next column.
     The room this takes comes from the introduction, whose track gives way
     first (see .mega-menu__inner).

     FIVE OR SIX LINKS TAKE THREE ROWS `[17 nov]`, so they make two columns
     and not three. The column stops at 560px, so three columns are about
     140px each at every width and break each title onto two or three
     lines: measured at 1536 and 1920, the panel stood 305px tall with three
     columns and 287px with two. */
  @media (min-width: 1280px) {
    .mega-menu__column:has(> .mega-menu__links > li:nth-child(3)) {
      flex-basis: 560px;
    }
    .mega-menu__links:has(> li:nth-child(3)) {
      display: grid;
      grid-template-rows: repeat(2, auto);
      grid-auto-flow: column;
      grid-auto-columns: minmax(min-content, 1fr);
      gap: var(--wp--preset--spacing--10) var(--wp--preset--spacing--60);
    }
    .mega-menu__links:has(> li:nth-child(5)) {
      grid-template-rows: repeat(3, auto);
    }
  }
  .mega-menu__desc {
    display: block;
    margin-top: var(--wp--preset--spacing--10);
    color: var(--wp--preset--color--text-body);
    font-size: var(--wp--preset--font-size--brod-liten);
    font-weight: 400;
    line-height: 1.5;
  }
}

/* In the hamburger panel. The columns stack under the open item, each label
   above its links, and the rows take the dropdown's filled block on the
   dark ground: the same numbers, measured there. */
@media (max-width: 955px) {
  .is-nav-enhanced .site-nav .nav-more[aria-expanded="true"] ~ .mega-menu {
    display: block;
    width: 100%;
    margin: 0 0 clamp(16px, 4vw, 24px);
    font-size: var(--wp--preset--font-size--ingress);
  }
  .mega-menu__intro,
  .mega-menu__card,
  .mega-menu__desc {
    display: none;
  }
  .mega-menu__column + .mega-menu__column {
    margin-top: var(--wp--preset--spacing--40);
  }
  /* Graphite 200 on graphite deep, 6.00:1; see --text-muted-on-dark. */
  .mega-menu__label {
    padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--40) var(--wp--preset--spacing--20) var(--wp--preset--spacing--60);
    color: var(--text-muted-on-dark);
  }
  .is-nav-enhanced .site-nav .mega-menu__links a {
    /* The fill 16px in and the words 16px inside it, 32px in all; see
       .sub-menu a. */
    margin-left: var(--wp--preset--spacing--40);
    padding: 10px var(--wp--preset--spacing--40);
    border-radius: var(--radius-button);
  }
  .is-nav-enhanced .site-nav .mega-menu__links a:hover,
  .is-nav-enhanced .site-nav .mega-menu__links a:focus-visible {
    background: var(--hairline-color-dark);
  }
  .is-nav-enhanced .site-nav .mega-menu__links a[aria-current="page"] {
    background: var(--wp--preset--color--ground);
    color: var(--wp--preset--color--text-strong);
  }
}

/* Main */
/* width 100% is load bearing, and it is the same fault the hero container
   had, one level up. As a flex item in the column body, main should
   stretch to the window. It did not: margin-inline auto disables stretch
   alignment, and an item with no width is then sized to its CONTENT and
   centred in whatever is left. Its content included the partner band's
   2848px track, so main measured 1440 at every window width, clamped only
   by .container's max-width, and the whole page scrolled sideways on a
   phone. A definite width makes the auto margins centre a box that is
   already the right size. Measured: 1440 before, 375 after, at 375. */
.site-main {
  width: 100%;
  max-width: var(--container-max);
  margin-inline: auto;
  padding: var(--wp--preset--spacing--70) var(--gutter) var(--wp--preset--spacing--90);
}

/* ------------------------------------------------------------------
   The content column, and the one place the editor was lying.

   theme.json declares contentSize 1080 and wideSize 1440. The editor obeys
   both, so an editor building a page sees the content at 1080. The front
   end had no rule for either and ran everything at the full 1440, which
   meant the page that published was not the page that was composed:
   looser, wider, and with every line length wrong.

   The figure lives in theme.json and nowhere else. The value below is a
   fallback for the case where the global stylesheet did not load at all,
   not a second place to edit.

   The column is left aligned rather than centred in the remaining space,
   because v.1 is explicit that everything is left aligned. That is the
   one place this deliberately differs from the editor, which centres.

   alignwide and alignfull are the escapes, so a block can still reach
   past the column when an editor asks it to.
   ------------------------------------------------------------------ */
.site-main:not(.site-main--home, .site-main--bands) > :not(.section, article),
.site-main:not(.site-main--home, .site-main--bands) > article > :not(.section),
.site-main:not(.site-main--home, .site-main--bands) > .container--narrow > :not(.section) {
  max-width: var(--wp--style--global--content-size, 1080px);
}
/* The article is a wrapper, not content: its children take the column one
   by one in the rule above. Constraining the article itself capped every
   band inside it at 1080 plus the gutters, measured at 1176 on a 1440
   window, and a band that stops there is a panel. */

/* A band is not content. The hero's picture and a dark band's ground are
   the page's own surface, and a surface that stops
   short of the edge is a panel. They break out of the column AND out of
   the gutter the main region pads with, so they run edge to edge.

   Edge means this region's edge, up to 1440, not the raw viewport.
   Reaching the window itself takes 100vw, and 100vw counts the scrollbar,
   so every one of these bands would add a horizontal scroll. The usual
   cure for that is overflow-x hidden on the page, which kills position
   sticky, and this theme has a sticky header and a sticky hero. The
   front page does not need the trick: its main region is already
   unconstrained, so the bands there do reach the window.

   Anything inside a band keeps its own container and its own measure. */
.site-main:not(.site-main--home, .site-main--bands) .section {
  width: auto;
  max-width: none;
  margin-inline: calc(var(--gutter) * -1);
}
.site-main:not(.site-main--home, .site-main--bands) :is(.alignwide, .alignfull) {
  max-width: var(--wp--style--global--wide-size, 1700px);
}
.site-main:not(.site-main--home, .site-main--bands) .alignfull {
  max-width: none;
}
/* The measure for running text.

   It has to exempt the layout components, because a paragraph and a list are
   also what several of them are built from, and the measure clips them
   without anything looking broken: a card row built from a ul stops at half
   its container, a section label written as a p gets a divider a third as
   long as one written as an h2.

   ADD TO THIS LIST when a component is a p, a ul or an ol and is not prose.

   The .txlog ones show how it looks when it happens: the transaction
   log is a panel built out of paragraphs, so the measure capped its tab row
   at 491 of 615 and its foot at 393. Neither looked like a text width
   problem. The row's rule simply stopped short of the panel's edge, and the
   foot's right hand word sat two thirds of the way across. Its step list
   was the fifth [22 okt]: capped at 683 of 850, the nodes bunched to the
   left while the rail, measured against the full track, ran past the last
   one. .dir-rows and .log-rows came next [26 okt], once the labelled bands
   stopped making a third track: at 1920 both lists stopped at 683 of 720
   and their rules ended 37px short of the panel head above them. And
   .log-steps__list the same day: the rail is drawn on .log-steps at full
   width, the dots on the capped list, so at 1920 the rail ran 48px past
   Levererad. Those two left the list with their panels [16 nov]; .dir-rows
   stays. A right aligned paragraph is the sixth [29 okt]: it aligns to
   the column's edge, and capped at 683 the start page's "Se alla
   systemintegrationer" ended halfway across, under nothing. The career
   page's job rows the seventh [30 okt]: at 1440 they stopped at 683 of
   1329, the chevrons in the middle of the page.

   The :where() around the :not() keeps the specificity where it was, so the
   exemption cannot start winning arguments it was not meant to be in. */
.site-main :where(p, ul, ol):where(:not(.section-label, .buttons, .flow-row, .contact-ways, .system-grid__slot, .check-list, .split-rows, .panel__foot, .record-row__text, .txlog__tabs, .txlog__foot, .txlog__focus-title, .txlog__steps, .dir-rows, .portal-window__title, .run-order__steps, .has-text-align-right, .job-list__items)) {
  max-width: var(--text-measure);
}

/* ------------------------------------------------------------------
   Footer.

   The design system's Footer: graphite 900, a brand cell with the mark
   and the tagline, then the link columns, a hairline, and the fine print
   row.
   ------------------------------------------------------------------ */
.site-footer {
  padding-block: var(--wp--preset--spacing--85) var(--wp--preset--spacing--65);
  background: var(--wp--preset--color--graphite-deep);
  color: var(--wp--preset--color--text-on-dark);
}
.site-footer a {
  color: var(--wp--preset--color--text-on-dark);
  text-decoration: none;
}
.site-footer a:hover {
  text-decoration: underline;
}

.site-footer__columns {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 200px), 1fr));
  gap: var(--wp--preset--spacing--70) var(--wp--preset--spacing--60);
  padding-bottom: var(--wp--preset--spacing--80);
  border-bottom: 1px solid var(--hairline-color-dark);
}

/* The contact column. The facts come from inc/company.php; what is here
   is the shape, which is the link columns' with the lines closer than
   their 12px because these are one address and not four destinations.
   Its heading takes the link columns' heading rule, further down. */
.site-footer__contact-lines {
  margin: 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.7;
  /* The same tone as the links in the columns beside it: a muted label
     over light content. Otherwise this column reads flatter than its
     neighbours. */
  color: var(--wp--preset--color--text-on-dark);
}
.site-footer__contact-lines a {
  color: inherit;
}

.site-footer__tagline {
  max-width: 30ch;
  margin: var(--wp--preset--spacing--45) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
  color: var(--text-muted-on-dark);
  text-wrap: pretty;
}

/* The footer menu, two levels deep. Each top level item is a column, its
   children are that column's links. The nav element itself is the grid
   item's parent, so it spans the columns and passes the grid through. */
.site-footer__nav {
  display: contents;
}
.site-footer__menu,
.site-footer__menu .sub-menu {
  margin: 0;
  padding: 0;
  list-style: none;
}
.site-footer__menu {
  display: contents;
}
/* One column. */
.site-footer__menu > li {
  display: flex;
  flex-direction: column;
  gap: var(--wp--preset--spacing--30);
}
/* The column heading. Set as a link in wp-admin, read as a label here.
   The contact column's heading is a paragraph rather than a link, and
   takes the same shape. */
.site-footer__menu > li > a,
.site-footer__heading,
.site-footer__contact-title {
  /* margin, not margin-bottom: an h2 brings a top margin of its own and
     the column would start lower than the two beside it. */
  margin: 0 0 6px;
  color: var(--text-muted-on-dark);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
}
.site-footer__menu .sub-menu {
  display: flex;
  flex-direction: column;
  gap: var(--wp--preset--spacing--30);
}
.site-footer__menu .sub-menu a {
  font-size: var(--wp--preset--font-size--brod-liten);
}

/* ------------------------------------------------------------------
   The footer columns as accordions, on a narrow window.

   Only where the toggle exists. Without scripting there is no button and
   this whole block is inert, so the columns stay open, which is what
   they are on a wide window too.
   ------------------------------------------------------------------ */
.footer-toggle {
  display: none;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  margin-inline-start: auto;
  padding: 0;
  border: 0;
  background: none;
  color: var(--text-muted-on-dark);
  cursor: pointer;
}

/* A plus that becomes a minus. Two bars, the upright one rotated away
   when the column opens. Drawn, not fetched: the design system's icons
   never stand alone. */
.footer-toggle__mark,
.footer-toggle__mark::before {
  display: block;
  width: 14px;
  height: 2px;
  background: currentColor;
}
.footer-toggle__mark::before {
  content: "";
  transform: rotate(90deg);
  transition: transform var(--dur-hover) var(--ease);
}
.footer-toggle[aria-expanded="true"] .footer-toggle__mark::before {
  transform: rotate(0deg);
}

/* Phones only. A tablet has room for the columns side by side, and folding
   them there would hide links behind taps for no gain in space. */
@media (max-width: 420px) {
  .is-nav-enhanced .footer-toggle {
    display: inline-flex;
  }

  /* The heading and its toggle share a row; the list is the row below. */
  .is-nav-enhanced .site-footer__menu > li {
    display: grid;
    grid-template-columns: 1fr auto;
    align-items: center;
    gap: 0;
  }
  .is-nav-enhanced .site-footer__menu > li > a,
  .is-nav-enhanced .site-footer__heading {
    margin-bottom: 0;
    padding-block: var(--wp--preset--spacing--30);
  }
  .is-nav-enhanced .site-footer__menu .sub-menu {
    grid-column: 1 / -1;
    display: none;
    padding-bottom: var(--wp--preset--spacing--40);
  }
  /* The open state reads off the button's own sibling, not :has(). A
     browser without :has() would drop the whole rule and leave a list
     that no button could ever open, which is worse than no accordion. */
  .is-nav-enhanced .site-footer__menu [aria-expanded="true"] ~ .sub-menu {
    display: flex;
  }

  /* A hairline under each column, so a shut accordion still reads as a
     row and not as a stray heading. */
  .is-nav-enhanced .site-footer__menu > li {
    border-bottom: 1px solid var(--hairline-color-dark);
  }
}

.site-footer__fine {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--wp--preset--spacing--30) var(--wp--preset--spacing--60);
  padding-top: var(--wp--preset--spacing--50);
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--text-muted-on-dark);
}
.site-footer__legal {
  margin: 0;
}
.site-footer__legal-nav ul {
  display: flex;
  flex-wrap: wrap;
  gap: var(--wp--preset--spacing--30) var(--wp--preset--spacing--60);
  margin: 0;
  padding: 0;
  list-style: none;
}
/* The legal links sit in the muted row and inherit its colour, so they
   are not brighter than the copyright beside them. */
.site-footer__legal-nav a {
  color: inherit;
}

/* The social tiles, last in the fine print row. Artwork approved as final
   [beslut användare 15 nov]: 26px tiles, 12px apart, graphite square,
   white mark. The tile is graphite on graphite-deep on purpose; the mark
   carries the contrast. margin-left: auto pushes the row to the far end
   on a wide screen; when the row wraps it starts a line of its own. */
.social-links {
  display: flex;
  gap: var(--wp--preset--spacing--30);
  margin: 0 0 0 auto;
  padding: 0;
  list-style: none;
}
/* Under .site-footer so it outranks .site-footer a, which sets every
   footer link white and would paint the square white with it. */
.site-footer .social-links__link {
  display: block;
  color: var(--wp--preset--color--graphite);
}
.social-links__link svg {
  display: block;
}
.social-links__glyph {
  fill: var(--wp--preset--color--text-on-dark);
}
.social-links__glyph--stroke {
  fill: none;
  stroke: var(--wp--preset--color--text-on-dark);
}

/* ------------------------------------------------------------------
   Section layer.

   [decision 17 Sep] Version 1 is light mode only. Dark surface is
   therefore emphasis and not ground, and is used in exactly two places:
   the closing CTA section and the footer. Add a third and the emphasis
   is gone.

   Rhythm is carried by hairlines and by sections having different
   heights, not by alternating white and light grey grounds. The grey was
   doing the job the hierarchy should do.
   ------------------------------------------------------------------ */

.site-main--home {
  max-width: none;
  padding: 0;
}

/* A page whose content is bands edge to edge is not a content column, so
   it does not take the column's width cap, its gutter or its vertical
   padding. It is the front page's arrangement on another template, and it
   is why this class is named in the :not() guards above alongside --home.

   THE WIDTH CAP IS WHAT MAKES THE BANDS REACH THE WINDOW. Capped at 1440,
   a band stops where the main region stops and leaves ground either side of
   it, while the footer, which sits outside main, runs to the edge: measured
   at a 2000px window, the dark band was 1440 wide against the footer's
   2000. Unconstraining the region is the same answer the front page uses,
   and it avoids 100vw, which counts the scrollbar and would put a sideways
   scroll on every band. The .container inside each band still holds the
   content to 1440 and adds the gutter, so nothing about the reading column
   changes. With it the first band starts 48px down
   the page and the last stops 96px short of the footer, and both gaps are
   ground that belongs to neither the band nor the thing next to it: a white
   stripe under the header, and a second one between a dark band and the
   dark footer.

   The bands carry their own rhythm in --section-pad, which is what the
   space between them is supposed to come from. This is the same thing
   .site-main--home does for the front page, minus the width, which a page
   with a title and a breadcrumb still wants. */
.site-main--bands {
  max-width: none;
  padding: 0;
}

.section,
.is-style-section,
.is-style-section-surface {
  padding-block: var(--section-pad);
}

/* The only light deviating surface on the page. Used once. */
.section--surface,
.is-style-section-surface {
  background: var(--wp--preset--color--surface);
  --field-surface: var(--wp--preset--color--surface);
  --field-tab: 1;
}

/* Emphasis. Inverts the whole section. Written into a pattern, never offered
   as a block style: see the note in inc/block-styles.php. */
.section--dark {
  background: var(--wp--preset--color--graphite-deep);
  color: var(--wp--preset--color--text-on-dark);
  --field-surface: var(--wp--preset--color--graphite-deep);
}

/* The contact page's closing band, one step lighter: graphite, which is the
   design file's own surface for it, where every other dark surface in the
   theme is graphite deep.

   IT SITS DIRECTLY ON THE FOOTER, which stays graphite deep, so there is a
   visible boundary between the two. That is the point of it rather than a
   consequence to live with: it separates the band a reader is meant to fill
   in from the chrome underneath, which the front page does not need because
   its closing band is a CTA and reads as part of the same dark foot.

   THE INK COMES FROM .section--dark ABOVE and was measured against
   graphite deep. Graphite is LIGHTER, so every one of those numbers goes
   down, not up, and they were remeasured rather than assumed:

                        on graphite deep   on graphite
     text-on-dark             15.73:1        12.52:1
     muted on dark             6.00:1         4.78:1
     hairline dark             1.65:1         1.31:1

   Both inks still clear 4.5:1, but the muted one clears it by a quarter of
   a point rather than a point and a half. It is not used in this band
   today, which carries a heading in text-on-dark and the plugin's form and
   nothing else. If prose in the muted colour is ever added here, that 4.78
   is the number to check against, not the 6.00 in the footer. */
/* Generalised: .section--contact-info was the first caller and is kept as a
   name so the markup already published does not have to change. Any band
   that wants graphite rather than graphite deep takes .section--graphite. */
.section--contact-info,
.section--graphite {
  background: var(--wp--preset--color--graphite);
  --field-surface: var(--wp--preset--color--graphite);
}
/* THE "MER INFORMATION" BAND, CENTRED [Emilie 23 okt], as the design draws
   it at the foot of the contact page: the symbol, the heading, the two
   fields side by side, the note and the button, all on the middle line.
   The fields' own text keeps to the left, where a reader types. */
/* Lower than a full band [Emilie 15 nov]: a heading and a two field form do
   not need 112px above and below. The same cap as the compact form band. */
.section--contact-info {
  padding-block: min(var(--section-pad), var(--wp--preset--spacing--80));
}
.section--contact-info > .container {
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
}
.section--contact-info > .container > * {
  margin-block: 0;
}
/* Room between the symbol and the heading [Emilie 23 okt]. Stated at the
   reset's own weight, which otherwise zeroes it. */
.section--contact-info > .container > .contact-info__mark {
  display: block;
  width: 48px;
  height: 48px;
  margin-bottom: var(--wp--preset--spacing--50);
}
.section--contact-info .form-slot {
  width: 100%;
  max-width: 45rem;
  margin-top: var(--wp--preset--spacing--60);
}
.section--contact-info .gform_wrapper input {
  text-align: start;
}
.section--contact-info .gform_footer {
  justify-content: center;
}
/* AND THE LAST DARK BAND ON A PAGE TAKES IT WITHOUT ASKING. It sits
   straight on the footer, which is graphite deep; the same colour on both
   makes the boundary disappear. The contact page said this by hand with
   the class above, and om-oss and erp-byte did not, so both ended in a
   band the eye could not tell from the footer.

   Two parents because the templates differ: a page pattern renders into
   main, the legal pages wrap their bands in an article. */
:is(.site-main, .site-main > article) > .section--dark:last-child {
  background: var(--wp--preset--color--graphite);
  --field-surface: var(--wp--preset--color--graphite);
}
/* Editor authored text may break inside a word for the same reason as a
   heading below, and with more cause: nobody controls what goes into it. A
   long address, a compound or a reference number spills out of its box
   WITHOUT the box growing, so nothing measures as overflowing and the page
   scrolls sideways anyway. The privacy policy did exactly that at 320. */
.block,
.policy-body {
  overflow-wrap: break-word;
}

/* A heading may break inside a word when the word is wider than the column.

   Swedish compounds get long: "standardintegration" is 19 characters, and at
   the heading sizes that is wider than a 265 pixel column at 320. The text
   then spills out of its box WITHOUT the box growing, so nothing measures as
   overflowing and the page still scrolls sideways. break-word rather than
   anywhere: it breaks only when the word cannot fit on a line of its own,
   which leaves normal wrapping alone. */
:is(h1, h2, h3, h4, .display) {
  overflow-wrap: break-word;
}

/* theme.json gives every heading text-strong as an element style, which
   beats what a dark section inherits, so the ink is stated here. The hero
   is a dark surface too: .hero__heading states its own colour, but any
   other heading on the film would come out graphite on graphite. */
.section--dark :is(h1, h2, h3),
.section--hero :is(h1, h2, h3) {
  color: var(--wp--preset--color--text-on-dark);
}

/* ------------------------------------------------------------------
   Hero.

   Full viewport, dark, content on the bottom edge. The design scales the
   headline down and settles it into the header while the page scrolls;
   assets/js/hero.js drives that with transforms. What is here is the hero
   at scroll position zero, which is where it starts and where it stays
   without the script.

   100svh, not 100vh: on a phone the browser chrome makes vh taller than
   the visible area, and the buttons would sit below the fold on first
   paint, which is the one thing this section cannot afford.
   ------------------------------------------------------------------ */
/* THREE LAYERS, each one the fallback for the one above it.

     3. the film        assets/media/hero.mp4, rendered only if the file is
                        there. Covers the image while it plays
     2. the still       assets/media/hero.jpg, painted by this rule. Shows
                        before the film has data, and instead of it if the
                        film is missing or refuses to play
     1. the colour      graphite deep, below both. Shows if the image 404s,
                        is still downloading, or is blocked

   The colour is declared on its own line rather than in a background
   shorthand, so a missing image cannot take it down with it. That is the
   whole point of the arrangement: white text on this section is only ever
   legible because something dark is behind it, and the colour is the only
   layer that cannot fail to load. */
.section--hero {
  /* Relative until the scroll script makes it sticky, see .is-live below.
     z-index 0 puts it under the sheet that follows and under the header. */
  position: relative;
  z-index: 0;
  isolation: isolate;
  overflow: hidden;

  /* Grid, not flex, and the difference is not cosmetic. A flex item is
     sized by its content and will not shrink below it, so the container
     in here stopped filling the row and started pushing past the window
     instead, which put a horizontal scroll on the whole page. A grid item
     stretches to its column and shrinks with it.

     The footer's missing right hand edge was that same overflow: with the
     page wider than the window, a full width band still only paints as
     far as the window goes. */
  display: grid;
  align-content: end;
  /* The header is transparent over this section, so the section has to be
     under the header or the transparent header would show the white body
     behind it. The negative margin pulls it up by the header's height, and
     the full 100svh then makes the hero exactly one screen. The top padding
     gives that height back inside, so on a short window the content still
     starts below the header rather than under it.

     Where the header cannot go transparent it stays solid and simply covers
     the top strip of the picture. The content sits at the bottom edge and
     is not affected.

     The pull is in a rule of its own below, scoped to the front page,
     because it is only correct where the header is transparent. */
  min-height: 100svh;
  padding-block: calc(var(--section-pad-hero) + var(--header-height)) clamp(72px, 12vh, 140px);
  background-color: var(--wp--preset--color--graphite-deep);
  background-image: url("assets/media/hero.jpg");
  background-size: cover;
  background-position: center;
  background-repeat: no-repeat;
  color: var(--wp--preset--color--text-on-dark);
}
/* STICKY ONLY WHILE assets/js/hero.js RUNS, so the white sheet below slides
   up over it instead of pushing it away. The script sets .is-live only when
   motion is allowed and the hero's links and buttons fit the window. A
   sticky hero never shows what lies below the window: the sheet covers it
   first, and on a low window or at 200% text that was the buttons (WCAG
   1.4.4, 1.4.10).
   Without the class, with no script or reduced motion, the hero scrolls
   away like any band. The film hero pages set relative again further down,
   with the same specificity, later. */
.section--hero.is-live {
  position: sticky;
  top: 0;
}

/* The film. Sits over the still, under the scrim.

   grayscale(1) is the design's own treatment, and it is what actually
   removes colour: a scrim only ever tints colour, it cannot take it away.
   The contrast lift puts back the separation that desaturating costs. */
.hero__film {
  position: absolute;
  inset: 0;
  z-index: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  filter: grayscale(1) contrast(1.05);
}

/* No film on a phone. The still is already behind it and carries the same
   image, so nothing is lost but the movement.

   Hiding it here is belt and braces: the element never receives a src
   below 768 in the first place, so there is nothing to fetch. This only
   makes sure an empty video element cannot paint over the image.

   A reader who asked for no motion keeps the element: hero.js never gives
   it a src, so it shows only its poster, which is the still. The front page
   below needs that, because there the poster is where the still lives on
   a wide window. */
@media (max-width: 767px) {
  .hero__film {
    display: none;
  }
}

/* THE FRONT PAGE FILM STOPS AT 1300 PX [Emilie 19 okt]. Wider than that it
   is centred and its side edges fade into the graphite behind it.

   The fade grows with the space outside the film, from nothing at 1300 to
   320 px at 1460, so it never switches on with a jump. The width is for the
   threads, which fade out across it. The film's background does not
   fade: it is not drawn at all, see the filter below.

   The section's still would otherwise run full width and show as a frozen
   strip on each side of the moving film, so where the film is in the page
   the still is taken off the section and carried by the film's poster,
   inside the same box and under the same fade. Where the film file is
   missing there is no poster, and the section keeps its still. */
/* The matrix the film's filter points at. Out of the flow so the grid
   gives it no row. */
.hero__film-tint {
  position: absolute;
}

@media (min-width: 768px) {
  .site-main--home .hero__film {
    /* A width and auto margins, not two insets and width auto: a video is
       a replaced element, and auto gives it the file's own width rather
       than the space between the insets. */
    width: min(100%, 1300px);
    margin-inline: auto;
  }

  .site-main--home .hero__film {
    /* THE FILM IS DRAWN AS LIGHT ON A TRANSPARENT GROUND [Emilie 19 okt],
       by one matrix, #hero-film-tint in blocks/hero.php. The threads keep
       graphite-900's blue-grey hue, contrast 1.05 and 0.65 opacity; the
       film's background becomes fully transparent, so what shows there
       is the section's own #1B242C, the same pixels as the sides.

       WHY NOT JUST MATCH THE COLOUR. A background even one level off the
       sides bands across the fade: a screen shows whole levels, and the
       browser does not dither a masked video the way it dithers a
       gradient. Eight levels gave eight flat bands. Matching the colour
       exactly worked here and failed on another machine, where the same
       file decoded one level darker and each channel flipped at its own
       place in the fade. Video decoding differs by graphics card and
       driver; a transparent ground does not depend on it. Tested at
       brightness 0.97 and 1.03: every pixel in the fade stays #1B242C.

       A new film needs its background luminance measured and put in the
       matrix's alpha row, see the comment there.

       One filter instead of a filter, a mix-blend-mode layer and
       opacity, because each of those is recomputed for every frame of
       the film. Measured with software rendering at 2560 wide, the
       three as layers gave 14 fps and 108 dropped frames in 6 s; the
       matrix gives 35 fps. With a graphics card both hold 60. */
    filter: url(#hero-film-tint);
  }

  .site-main--home :is(.hero__film, .hero__flow) {
    /* Eased, not linear. A straight ramp starts and stops with a corner,
       and the eye reads each corner as an edge: that was the seam. These
       stops are smoothstep, 3t² minus 2t³, sampled in eighths. */
    mask-image: linear-gradient(
      to right,
      rgb(0 0 0 / 0) 0,
      rgb(0 0 0 / 0.043) calc(var(--hero-film-fade) * 0.125),
      rgb(0 0 0 / 0.156) calc(var(--hero-film-fade) * 0.25),
      rgb(0 0 0 / 0.316) calc(var(--hero-film-fade) * 0.375),
      rgb(0 0 0 / 0.5) calc(var(--hero-film-fade) * 0.5),
      rgb(0 0 0 / 0.684) calc(var(--hero-film-fade) * 0.625),
      rgb(0 0 0 / 0.844) calc(var(--hero-film-fade) * 0.75),
      rgb(0 0 0 / 0.957) calc(var(--hero-film-fade) * 0.875),
      rgb(0 0 0 / 1) var(--hero-film-fade),
      rgb(0 0 0 / 1) calc(100% - var(--hero-film-fade)),
      rgb(0 0 0 / 0.957) calc(100% - var(--hero-film-fade) * 0.875),
      rgb(0 0 0 / 0.844) calc(100% - var(--hero-film-fade) * 0.75),
      rgb(0 0 0 / 0.684) calc(100% - var(--hero-film-fade) * 0.625),
      rgb(0 0 0 / 0.5) calc(100% - var(--hero-film-fade) * 0.5),
      rgb(0 0 0 / 0.316) calc(100% - var(--hero-film-fade) * 0.375),
      rgb(0 0 0 / 0.156) calc(100% - var(--hero-film-fade) * 0.25),
      rgb(0 0 0 / 0.043) calc(100% - var(--hero-film-fade) * 0.125),
      rgb(0 0 0 / 0) 100%
    );
  }

  /* No mood layer behind the film. Its soft gradients are dithered by the
     browser, and at this darkness the dither reads as vertical streaks:
     measured, it was all of the texture on the sides and most of it in the
     fade. Its job is depth when there is no film; here there is one. */
  .site-main--home .section--hero:has(.hero__film)::before {
    content: none;
  }

  .site-main--home .section--hero:has(.hero__film) {
    --hero-film-fade: clamp(0px, (100vw - 1300px) * 2, 320px);
    background-image: none;
  }

  /* The fade starts where the window outgrows the content column, the
     same way the film's starts at 1300. */
  .site-main--home .section--hero:has(.hero__flow) {
    --hero-film-fade: clamp(0px, (100vw - var(--hero-flow-max)) * 2, 320px);
  }
}

/* THE MOVING THREAD [13 nov]. The front page draws the thread live,
   assets/js/syncify-flow.js, on a transparent canvas over the section's
   graphite. It replaces the film there and runs at every width: it
   downloads nothing, so the phone rule that kept the film off small
   windows has nothing to save.

   THE STILL IS THE FALLBACK, and it is taken off the section only while
   the thread can draw. :defined is false while the deferred script has not
   run, and stays false if it is blocked or fails; [unsupported] is set by
   the element itself when there is no WebGL or a shader will not compile.
   In each of those cases this rule does not match and the still, the
   film's first frame, stays where style.css and inc/media.php paint it.
   The mood layer goes with it, for the same reason as over the film.

   prefers-reduced-motion is not a failure: the element draws the loop's
   first frame and holds it, so the still is not needed then either. */
.hero__flow {
  z-index: 0;
}

/* ONE SHAPE AT EVERY SIZE [Emilie 13 nov]. The thread is drawn in
   fractions of its own box, so a box that changed shape with the window
   squeezed the thread on a phone and stretched it on a short laptop. The
   box keeps one proportion instead, the full height of the hero and
   1.485 times as wide, and is centred: a window narrower than that cuts
   it off at both sides, like a picture set to cover, and the thread runs
   on past the screen's edges.

   1.485 is the shape approved on a full screen, 1920 by 1080, where the
   box was the content column, 1604 by 1080.

   It never gets narrower than the content column, or the window if that
   is narrower, so on a wide and short window the thread still reaches the
   text's edges. That is the one case where the shape gives: the box is
   then wider than 1.485. On a window taller than 1080 at 1920 the box
   grows past the column instead, and the fade above takes the edge.

   Centred with left and translate, not auto margins: an absolutely
   placed box wider than its container ignores auto margins and sits at
   the left. The width comes from aspect-ratio against the height the
   insets give. */
.site-main--home .section--hero:has(.hero__flow) {
  --hero-flow-max: calc(var(--container-max) - 2 * var(--gutter));
}

.site-main--home .hero__flow {
  right: auto;
  left: 50%;
  width: auto;
  min-width: min(100%, var(--hero-flow-max));
  aspect-ratio: 1.485;
  translate: -50% 0;
}

.site-main--home .section--hero:has(.hero__flow:defined:not([unsupported])) {
  background-image: none;
}

.site-main--home .section--hero:has(.hero__flow:defined:not([unsupported]))::before {
  content: none;
}

/* Legibility, and how much of the film is allowed through.

   Three dials, so this is one number to change rather than five. Raise
   them to sink the film further into the surface, lower them to let more
   of it read. Colour is already gone at the source, by the grayscale on
   the film itself; these only control how much FORM survives.

   --hero-veil        flat coverage over the whole section
   --hero-scrim-*     extra darkness, heaviest at the bottom where the
                      headline sits, lightest at the top */
.section--hero {
  /* PRELIMINARY, 5 okt, pending a new film. 85 per cent coverage is a
     trade against the file's own compression artefacts: 92 per cent of the
     picture lies below level 64, where H.264 blocks, and the block steps
     measure 1.24 against their surroundings. At 70 per cent coverage the
     steps were 0.66 on screen, at 85 they are 0.33, and the film still
     shows five times more clearly than at 97. The figures and how they
     relate are in ATT-GORA.md. */
  --hero-veil: 45%;
  --hero-scrim-bottom: 73%;
  --hero-scrim-mid: 56%;
  --hero-scrim-top: 31%;
}
/* The mood layer. Sits over the film and under the scrim, and gives the
   surface depth when there is no film at all, which is what it mostly
   earns its place doing. Graphite tones only: the design system is explicit
   that the hero's layers are film, graphite, tone, and never a colourful
   gradient.

   At the scrim strength above, very little of this reaches the eye. It is
   painted once and never per frame, so it costs nothing to keep, and it is
   the difference between a flat panel and a lit one on the day the film is
   missing. */
.section--hero::before {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 1;
  pointer-events: none;
  opacity: 0.38;
  background:
    radial-gradient(ellipse 60% 70% at 25% 40%, var(--graphite-400) 0%, transparent 70%),
    radial-gradient(ellipse 50% 60% at 80% 75%, var(--graphite-500) 0%, transparent 70%),
    radial-gradient(ellipse 70% 60% at 60% 10%, var(--wp--preset--color--graphite-deep) 0%, transparent 70%),
    linear-gradient(160deg, var(--graphite-800) 0%, var(--wp--preset--color--graphite) 45%, var(--graphite-600) 100%);
}

.section--hero::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 2;
  pointer-events: none;

  /* The flat veil and the gradient are separate declarations, not one
     background shorthand. If the gradient ever fails to parse, the veil
     survives on its own and the headline still has something dark behind
     it. In a shorthand one bad layer takes the whole scrim with it, and
     white text lands on the raw film. */
  background-color: color-mix(in srgb, var(--wp--preset--color--graphite-deep) var(--hero-veil), transparent);
  background-image:
    linear-gradient(
      to top,
      color-mix(in srgb, var(--wp--preset--color--graphite-deep) var(--hero-scrim-bottom), transparent) 0%,
      color-mix(in srgb, var(--wp--preset--color--graphite-deep) var(--hero-scrim-mid), transparent) 55%,
      color-mix(in srgb, var(--wp--preset--color--graphite-deep) var(--hero-scrim-top), transparent) 100%
    );
}
/* NO SCRIM ON THE FRONT PAGE [Emilie 13 okt]. The film shows as it is.
   The other pages that carry this hero keep it.

   WHAT HOLDS THE HEADLINE UP NOW IS THE PICTURE, not this rule. The
   still, the film's first frame, measures 32 of 255 on average where the
   headline stands at 1440x900 and 84 at its brightest, where a thread
   passes behind it: white text is 7.6:1 there and 11.5:1 or better over
   99 per cent of the area. That is a
   property of the file: a lighter still or film under the front page
   reopens the contrast question, which the scrim used to answer for any
   image. See assets/media/README.md. */
.site-main--home .section--hero::after {
  content: none;
}

/* width 100% is the line that puts the text back on the left. In a grid,
   auto margins beat stretch alignment, so a container with margin-inline
   auto and no width is sized to its content and centred in whatever is
   left over. Given a definite width it fills the column, stops at its
   own max-width, and the text sits at the gutter like every other section. */
.section--hero > .container {
  position: relative;
  z-index: 3;
  width: 100%;
}

/* The sheet. Everything after the hero rides up over it on scroll, which is
   the whole reason the hero is sticky rather than simply tall. It needs its
   own background: without one the hero would show through the gaps between
   sections.

   There is no wrapper element. The sections are blocks and sit directly in
   main, so each section after the hero is its own piece of sheet: same
   background, same layer, and contiguous sections make one surface.

   Also for a bands page that opens on the film hero: --film-hero marks
   one, and without the sheet the sticky hero would show through every
   section above it.

   A SECTION THAT BRINGS ITS OWN SURFACE IS ALREADY ITS OWN SHEET, and has
   to be excluded or this rule paints over it: it is one class more
   specific than .section--dark, so the closing dark band on a film hero
   page would come out white with white ink on it.

   ONLY THE ONES THAT REALLY SET A BACKGROUND. .section--contact does not:
   its ribbon is a pseudo element with nothing behind it, so excluding it
   leaves the front page's closing band transparent with the sticky hero
   showing through. Check the computed background, not the class name.

   ADD TO THIS LIST when a section modifier starts carrying a background. */
:is(.site-main--home, .site-main--film-hero) > :not(.section--hero, .section--dark, .section--surface) {
  position: relative;
  z-index: 1;
  background: var(--wp--preset--color--ground);
}
/* The excluded ones still need the layer, just not the colour. */
:is(.site-main--home, .site-main--film-hero) > :is(.section--dark, .section--surface) {
  position: relative;
  z-index: 1;
}

/* The hero sits UNDER the header, but only where the header is transparent,
   which is the front page and nowhere else (.site-header--over-hero, set in
   header.php on the same condition). The block is in the inserter for every
   page, so this was worth scoping: unscoped, a hero inserted on an ordinary
   page pulled itself up by 72px under a SOLID header, which covered its top
   strip and dragged the page title along with it. */
.site-main--home > .section--hero {
  margin-top: calc(var(--header-height) * -1);
}

/* THE TWO FILM HERO PAGES ARE NOT THE FRONT PAGE [Emilie 6 okt]. They
   take the same band, but only the front page opens on a band sized to the
   window.

   Three things come off together, because they are one arrangement:

     relative   the sticky hero exists so the sheet below can slide over a
                band that fills the screen. A band that is its own height
                is simply pushed away, which is the ordinary behaviour.
                Relative and not static [6 nov]: the film and the two
                pseudo element layers are absolute with inset 0, and with
                a static band they took the page as their box and reached
                up behind the header. The solid header hid it; the bare
                one showed the dark under dark ink.
     min-height the band is as tall as what is in it.
     padding    the base rule's top padding adds the header's height, to
                give back the room the front page's pull up takes. With no
                pull there is nothing to give back, so it is the ordinary
                band rhythm.

   These pages take the over-ground header with white ink over a pulled
   up band, see "Over a dark opening band" [Emilie 6 nov]. Not over-hero,
   whose swap is a range written against 100svh and would stay white past
   the end of these bands. */
.site-main--film-hero > .section--hero {
  position: relative;
  min-height: 0;
  padding-block: var(--section-pad);
}

/* EVERY PAGE OPENS AT ONE OF FOUR HEIGHTS [Emilie 5 nov]. Each hero was as
   tall as its own words, 364 to 771px at 1440, and the heading started
   anywhere from 184 to 284px down, so moving between pages jumped.

     front page      100svh, set on .section--hero above
     with a log      820px, 750px from 1440; a hero holding a .panel or
                     .panel-bed
     other pages     670px, the first section of any other bands page,
                     and the integration hero
     policy pages    420px, still lower than the rest [Emilie 6 okt]; also
                     .section--short-hero, /karriar/ [Emilie 10 nov], whose
                     words are a heading and two buttons, centred, and
                     /sparbarhet/, a heading and a lead [Emilie 16 nov]

   THE LOG TIER HAS TWO STEPS because its tallest hero moves with the
   width. Measured 5 nov from 1024 to 1920, the reconciliation page's lead
   wraps to more lines between 1300 and 1420 and peaks at 815px near 1380;
   from 1440 up the tallest of the four is 741 (ERP, at 1920). One value of
   820 would have left 200px more band than needed on every wide screen.
   The diagram on the ERP page was drawn lower the same day for this.

   "The first section" assumes a bands page opens on its hero, which every
   page pattern does. A page on template-bands.php that opens on something
   else gets the floor too. The contact page is outside the tiers on
   purpose: its first child is an <article> and its one section is the
   whole page, 1400px and more, not a hero.

   SAME HEIGHT, WRITTEN AS A FLOOR. Each value is just above the tallest
   hero in its tier as measured on 5 nov, so every hero in the tier comes
   out exactly that tall. min-height and not height because the hero
   clips its overflow for the film and the ribbons: a fixed height would
   cut the words off at 200% text zoom or after an editor lengthens a
   lead. A hero that outgrows its tier shows up as taller instead, and is
   the signal to remeasure; an integration with a long name is the
   likeliest.

   From 1024 only. Below that the columns stack and the heroes run from
   250 to 860px on a phone with what is in them; one floor would leave the
   short ones with a screen of empty band. The top alignment holds at all
   widths.

   The ribbon's reach is added because it is padding the next section takes
   back with a negative margin (see THE RIBBON ENDS ON THE NEXT LABEL'S
   RULE): without it /karriar/ would end 147px short of its tier. The
   header's height is added on the integration hero because that one is
   pulled up under the header and starts 72px higher than the rest, and
   on a dark opening band through --header-pull for the same reason (see
   "Over a dark opening band"). */
@media (min-width: 1024px) {
  .site-main--bands > section:first-child:not(:has(.panel, .panel-bed, .portal-figure)) {
    min-height: calc(670px + var(--ribbon-reach, 0px) + var(--header-pull, 0px));
  }
  .section--integration-hero {
    min-height: calc(670px + var(--header-height));
  }
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) {
    min-height: calc(820px + var(--header-pull, 0px));
  }
  .section--policy-hero {
    min-height: 420px;
  }
  /* The cookie page only, see syncify_legal_page(): no lead, so the floor
     left a heading and a date over an empty band [Emilie 13 nov]. */
  .section--policy-hero-short {
    min-height: 0;
  }
  /* The policy tier's height, with the words centred in it rather than at
     the top [Emilie 10 nov]: at 670 a heading and two buttons sat over
     500px of empty band. The selector matches the tier rule's weight so it
     wins by order. Centring works on the content box, and the ribbon's
     reach is bottom padding, so the words land in the middle of the band
     the reader sees, not of the band plus the reach. */
  .site-main--bands > section.section--short-hero:first-child {
    display: flex;
    flex-direction: column;
    justify-content: center;
    min-height: calc(420px + var(--ribbon-reach, 0px));
  }
  /* A flex item with auto inline margins shrinks to its content, which
     moved the heading off the left edge every section starts on. */
  .section--short-hero > .container {
    width: 100%;
  }
}
@media (min-width: 1440px) {
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) {
    min-height: calc(750px + var(--header-pull, 0px));
  }
}
/* THE WORDS SET THE LOG TIER, NOT THE PICTURE [Emilie 5 nov]. Every use
   case page is its tier's height, and an illustration taller than that
   hangs out of the hero over the next band, which she accepted for the
   process and ERP pages. Measured the same day: the words stay under the
   floor at every width from 1024, the portal window on the process page
   does not from about 1700.

   The picture stops counting by an equal negative margin above and below,
   which takes it out of the row's height without taking it out of the grid,
   and centred in its column like the words [Emilie 5 nov]: the margins are
   equal, so the box itself stands in the middle. 1000px is more than any
   panel is tall; a panel taller still would push the hero again, not
   break it. One taller than the hero hangs out at both ends.

   The hero then lets it out at the bottom and keeps clipping at the sides
   (overflow-x: clip leaves y visible, where hidden would not), and the
   picture is lifted over the next band. The next band is positioned so it
   paints over the flow figure behind the process page's card, which would
   otherwise trail down into it. */
@media (min-width: 1024px) {
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) {
    overflow-x: clip;
    overflow-y: visible;
  }
  .site-main--bands > section:first-child > .container > .band-head > :is(.panel, .panel-bed, .portal-figure),
  .site-main--bands > section:first-child > .band-head > :is(.panel, .panel-bed, .portal-figure) {
    align-self: center;
    margin-block: -1000px;
  }
  /* The bed gets no z-index: that would lift its flow figure with it. Its
     card is already z-index 1, see BOTH CARDS. */
  .site-main--bands > section:first-child .band-head > :is(.panel, .portal-figure) {
    position: relative;
    z-index: 1;
  }
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) + section {
    position: relative;
  }
  /* A band with no colour of its own is transparent, and the figure showed
     through it (tested 5 nov with the window drawn 900px tall). The page's
     ground, at no specificity, so a band that has a colour keeps it. */
  :where(.site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) + section) {
    background-color: var(--wp--preset--color--ground);
  }

  /* THE WORDS STAND IN THE MIDDLE OF THE HERO [Emilie 5 nov], the heading,
     the lead and the buttons as one block, centred between the hero's top
     and bottom padding. This departs from the tier's shared heading line
     (see THE HEADING STARTS AT THE SAME HEIGHT) on the use case pages only:
     the heading now moves with how long the lead is.

     The hero is made a grid that stretches its one row to the floor, so
     the band head is as tall as the hero and has a middle to centre in.
     Grid already on the reconciliation page, which layers its film in the
     same cell; block on the other three, where nothing depends on it. */
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) {
    display: grid;
    align-content: stretch;
  }
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) .band-head > :first-child {
    align-self: center;
  }
  /* Full width in the grid. The container centres itself with auto margins,
     and in a grid cell auto margins shrink it to its content: on the process
     page the content is a window zoomed to its own container, so the band
     head came out 745px wide in a 1009px hero and the window at 0.75. */
  .site-main--bands > section:first-child:has(.panel, .panel-bed, .portal-figure) > .container {
    width: 100%;
  }
}
/* THE PORTAL WINDOW GOES UNDER THE BUTTONS WHERE ITS COLUMN IS TOO NARROW
   [Emilie 5 nov]. Beside the words the window is zoomed to its column, and
   at 1024 that drew the 879px windows at half size, their 12px text at 6.
   Where the column would draw a window under 70 per cent, the band head is
   one column instead and the window stands full size under the buttons.

   The widths are where the column reaches 70 per cent of the window,
   measured 5 nov (the column is 437px at 1024 and 637 at 1440):
     run order, 879px, in the process page's bed     under 1440
     parallel run 727px and order record 696px       under 1180
   The second pair stand straight in the band head, which is how the rule
   tells them from the first.

   Stacked, the window is in the flow again: it counts towards the hero's
   height, so these heroes are taller than their tier's 820 there, and the
   process page's flow figure goes, as it does wherever the bed is under the
   words.

   NO LOWER BOUND [6 nov]. The band head keeps two columns down to about
   972, where two 420px tracks and the gap still fit, so a rule that began
   at 1024 left the window beside the words and small between 972 and
   1023. Below 972 the band head stacks by itself and these rules agree. */
@media (max-width: 1439.98px) {
  .site-main--bands > section:first-child > .band-head:has(> .panel-bed > .portal-figure) {
    grid-template-columns: minmax(0, 1fr);
  }
  .site-main--bands > section:first-child > .band-head:has(> .panel-bed > .portal-figure) > .panel-bed {
    align-self: auto;
    margin-block: 0;
  }
  .panel-bed:has(> .portal-figure)::before {
    display: none;
  }
}
@media (max-width: 1179.98px) {
  .site-main--bands > section:first-child > .band-head:has(> .portal-figure) {
    grid-template-columns: minmax(0, 1fr);
  }
  .site-main--bands > section:first-child > .band-head:has(> .portal-figure) > .portal-figure {
    align-self: auto;
    margin-block: 0;
  }
}
/* THE HEADING STARTS AT THE SAME HEIGHT ON EVERY PAGE OF A TIER, so the
   content stands at the top and the floor's extra ground goes underneath.
   This replaces three centrings in the hero, and only there: the band head
   with buttons [6 okt, see A BAND HEAD WITH BUTTONS CENTRES], the about
   page's three columns [26 okt] and the process page's card. Centred, the
   heading dropped 25 to 100px on the ERP, process and about pages.

   align-content undoes the film hero's bottom alignment, which a floor
   would otherwise turn into a heading at the foot of the band. The margin
   is the block gap WordPress puts after the film's <video>, which pushed
   the reconciliation page's heading 24px below the rest. */
.site-main--bands > section:first-child {
  align-content: start;
}
.site-main--bands > section:first-child > .band-head,
.site-main--bands > section:first-child > .container > .band-head {
  align-items: start;
  margin-block-start: 0;
}

/* Both transforms grow from the top left corner, so the headline shrinks
   towards the point it is travelling to rather than towards its own middle. */
.hero__heading,
.hero__actions {
  transform-origin: top left;
}

/* will-change only while the script is actually driving them. Each one buys
   a compositor layer, and a layer costs memory whether or not anything is
   moving. On a page with no script, or for a reader who asked for no motion,
   neither class is ever added. */
.section--hero.is-live .hero__heading {
  will-change: transform;
}
.section--hero.is-live .hero__actions {
  will-change: transform;
}

/* The headline is the largest thing on the site by a wide margin. The
   design asks for up to 150px, well past the display-1 preset's 68px
   ceiling, so the size is stated here rather than in theme.json: it is
   one heading on one section, not a step on the scale.
   Written with a rem term, never vw alone. A pure viewport unit does not
   grow when the reader zooms the page, which fails WCAG 1.4.4 Resize Text
   at 200 percent, which is also why there is no vh cap: a tall headline
   makes the hero taller, which min-height allows. */
.hero__heading {
  max-width: 15ch;
  margin: 0;
  color: var(--wp--preset--color--text-on-dark);
  font-size: clamp(2.5rem, 5.5vw + 1rem, 9.375rem);
  font-weight: 300;
  line-height: 1.12;
  letter-spacing: -0.02em;
  text-wrap: balance;
}
/* The emphasis inside the headline. Weight, never colour. */
.hero__heading b,
.hero__heading strong {
  font-weight: 500;
}
.hero__actions {
  margin-top: clamp(24px, 4vh, 48px);
}

/* The scroll cue at the foot of the hero, from the mobile design. A link
   to the next section, so it does something rather than only pointing.
   The chevron is drawn, not fetched: the design system's icons never
   stand alone, and this one has nothing beside it but its hidden label.
   Shown only where the header has already folded, since that is the
   design it comes from. */
.hero__scroll {
  display: none;
  position: absolute;
  left: 50%;
  bottom: 20px;
  z-index: 3;
  width: 44px;
  height: 44px;
  align-items: center;
  justify-content: center;
  translate: -50% 0;
  color: var(--wp--preset--color--text-on-dark);
}
.hero__scroll-mark {
  display: block;
  width: 12px;
  height: 12px;
  border-right: 2px solid currentColor;
  border-bottom: 2px solid currentColor;
  rotate: 45deg;
  translate: 0 -3px;
}
@media (max-width: 880px) {
  .hero__scroll {
    display: inline-flex;
  }
}

/* Buttons */
.buttons,
.wp-block-buttons.buttons {
  display: flex;
  flex-wrap: wrap;
  gap: var(--wp--preset--spacing--30);
  margin-top: var(--wp--preset--spacing--60);
}
/* On a phone the buttons stack and each takes the full width, as the
   mobile design draws them. A 35 character label otherwise wraps inside
   a button that is narrower than its own text. */
@media (max-width: 420px) {
  .buttons > .button,
  .buttons > .wp-block-button,
  .buttons .wp-block-button__link {
    flex: 1 1 100%;
    justify-content: center;
  }
}
.button,
.wp-block-button .wp-block-button__link {
  display: inline-flex;
  align-items: center;
  gap: var(--wp--preset--spacing--20);
  min-height: var(--field-height);
  /* A label that wraps, as a 35 character one does on a phone, gets its
     own line height and air above and below instead of the body's 1.6
     pressed against the border, and its lines centred instead of the
     second hugging the left edge. A one line label is unchanged: 12px
     above and below plus one line at 1.3 stays inside the 48px minimum,
     and text-align does not move a line that is as wide as its text. */
  padding: var(--wp--preset--spacing--30) var(--wp--preset--spacing--50);
  line-height: 1.3;
  text-align: center;
  border: 1px solid var(--wp--preset--color--graphite);
  border-radius: var(--radius-button);
  background: var(--wp--preset--color--graphite);
  color: var(--wp--preset--color--text-on-dark);
  font-weight: 500;
  text-decoration: none;
  transition: background var(--dur-hover) var(--ease);
}
.button:hover,
.wp-block-button .wp-block-button__link:hover {
  background: var(--wp--preset--color--graphite-deep);
  border-color: var(--wp--preset--color--graphite-deep);
}
/* Active state. Pressing must be visible on its own, not only through
   hover: a touch device has no hover, and a keyboard activation shows
   nothing otherwise. No transform, the design system has no motion on
   press; the surface darkens instead.

   Derived from the token rather than written as a new hex. The palette
   has no step below graphite-deep, and inventing one here would put a
   colour in the theme that the design system does not know about. If
   v.1 names a pressed colour, replace this with that token.
   [proposal] The 12% step is chosen to be visible, not specified. */
.button:active,
.wp-block-button .wp-block-button__link:active {
  background: color-mix(in srgb, var(--wp--preset--color--graphite-deep) 88%, #000);
  border-color: color-mix(in srgb, var(--wp--preset--color--graphite-deep) 88%, #000);
}
/* The compact size, for the header and other dense rows. Still 44px tall,
   which is the smallest a touch target may be. 8px above and below, not 0,
   so a label that wraps keeps air against the border; one line at 14px and
   1.3 is 18px, so 8 + 18 + 8 and the border stay inside the 44. */
.button--sm {
  min-height: 44px;
  padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--45);
  font-size: var(--wp--preset--font-size--brod-liten);
}

.button--outline,
.is-style-secondary .wp-block-button__link {
  background: transparent;
  color: var(--wp--preset--color--text-strong);
}
.button--outline:hover,
.is-style-secondary .wp-block-button__link:hover {
  background: var(--wp--preset--color--surface);
  border-color: var(--wp--preset--color--graphite);
}
.button--outline:active,
.is-style-secondary .wp-block-button__link:active {
  background: var(--wp--preset--color--hairline);
  border-color: var(--wp--preset--color--graphite);
}
/* Outline on a dark surface. The border is held back from full white so
   it reads as secondary next to .button--light, which is solid. */
.button--ghost,
.is-style-ghost .wp-block-button__link {
  background: transparent;
  border-color: color-mix(in srgb, var(--wp--preset--color--text-on-dark) 70%, transparent);
  color: var(--wp--preset--color--text-on-dark);
}
.button--ghost:hover,
.is-style-ghost .wp-block-button__link:hover {
  background: color-mix(in srgb, var(--wp--preset--color--text-on-dark) 12%, transparent);
  border-color: var(--wp--preset--color--text-on-dark);
}
.button--ghost:active,
.is-style-ghost .wp-block-button__link:active {
  background: color-mix(in srgb, var(--wp--preset--color--text-on-dark) 20%, transparent);
  border-color: var(--wp--preset--color--text-on-dark);
}

.button--light,
.is-style-light .wp-block-button__link {
  background: var(--wp--preset--color--ground);
  border-color: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
}
.button--light:hover,
.is-style-light .wp-block-button__link:hover {
  background: var(--wp--preset--color--surface);
  border-color: var(--wp--preset--color--surface);
}
.button--light:active,
.is-style-light .wp-block-button__link:active {
  background: var(--wp--preset--color--hairline);
  border-color: var(--wp--preset--color--hairline);
}

/* "Grafikaccent": the filled button in graphite 300, the palette's graphic.
   White on #5B7A8C measures 4.56:1, so the label clears 4.5:1 with almost
   nothing to spare. Keep the ink text-on-dark (#FFFFFF): the ground colour
   #FAFAFA on this fill falls to 4.36:1 and fails.

   Hover and press are derived towards graphite deep, as the primary's press
   is, because the scale has no named step just below graphite 300 that is
   far enough from it to see. [proposal] The 15% and 30% steps are chosen to
   be visible, not specified. */
.is-style-accent .wp-block-button__link {
  background: var(--wp--preset--color--graphic);
  border-color: var(--wp--preset--color--graphic);
  color: var(--wp--preset--color--text-on-dark);
}
.is-style-accent .wp-block-button__link:hover {
  background: color-mix(in srgb, var(--wp--preset--color--graphic) 85%, var(--wp--preset--color--graphite-deep));
  border-color: color-mix(in srgb, var(--wp--preset--color--graphic) 85%, var(--wp--preset--color--graphite-deep));
}
.is-style-accent .wp-block-button__link:active {
  background: color-mix(in srgb, var(--wp--preset--color--graphic) 70%, var(--wp--preset--color--graphite-deep));
  border-color: color-mix(in srgb, var(--wp--preset--color--graphic) 70%, var(--wp--preset--color--graphite-deep));
}

/* Core buttons written in the editor are the same buttons. The selectors
   above carry the theme's rules onto .wp-block-button__link; what remains is
   undoing what core's own stylesheet sets that the theme does not want: a
   larger font. Line height and alignment are the theme's own, set above.
   Block styles (inc/block-styles.php) map to the variants above:
   is-style-light, is-style-ghost, is-style-secondary, is-style-accent. */
.wp-block-button .wp-block-button__link {
  font-size: inherit;
}

/* Core's flow layout puts the block gap, 24px, between the children of every
   group. Where the theme lays the children out itself, in a grid or a flex
   row, that gap would be added to the theme's own, and it was: measured +24
   in the ownership grid and +48 in the stacked columns. The theme's layout
   components own the spacing of their children; core's rule has no
   specificity (:where) and one class is enough to switch it off. */
.ownership > *,
.columns > *,
.buttons > *,
.flow-row > *,
.split-rows > * {
  margin-block: 0;
}

/* "Med pil": the arrow beside the text, from the Heroicons arrow-right path as
   a mask, so it takes the button's ink and needs no markup an editor could
   break. Icons sit beside text, never alone, and never in the signal colour.

   THE PATH IS A COPY of arrow-right in inc/icons.php, which is the source.
   Change it there and here. Same for the .has-icon-* masks further down.
   The flow card's title arrow shares this rule; its size is under
   .flow-card. */
.is-style-arrow .wp-block-button__link::after,
.flow-card__title:has(a)::after {
  content: "";
  flex: none;
  width: 18px;
  height: 18px;
  background-color: currentColor;
  -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M13.5 4.5 21 12m0 0-7.5 7.5M21 12H3'/%3E%3C/svg%3E") center / contain no-repeat;
  mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M13.5 4.5 21 12m0 0-7.5 7.5M21 12H3'/%3E%3C/svg%3E") center / contain no-repeat;
}

.lead,
.is-style-lead {
  max-width: 62ch;
  margin-top: clamp(24px, 3vw, 40px);
  font-size: clamp(1rem, 0.6vw + 0.65rem, 1.1875rem);
  line-height: 1.6;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}

/* Section headings. The design runs a second display size below the hero,
   larger than the display-2 preset, so it is stated here for the same
   reason the hero's is: it belongs to the page, not to the scale. */
.display,
.is-style-display,
.is-style-display-sub {
  max-width: 16ch;
  margin: 0;
  font-size: clamp(2.125rem, 3.5vw + 0.75rem, 4.25rem);
  font-weight: 400;
  line-height: 1.1;
  letter-spacing: -0.02em;
  text-wrap: balance;
}
.display--sub,
.is-style-display-sub {
  max-width: 20ch;
  font-size: clamp(1.875rem, 2.5vw + 0.75rem, 3.25rem);
  line-height: 1.12;
}

/* The page heading, one step above a section heading.

   A page h1 and a section h2 both carried .display--sub and both measured
   48px at 1440, so the page read as a list of equals with no top. The step
   is stated at both ends of the clamp rather than only at the top, because
   at 360 the two sizes were 34 and 30px, which is not a step anyone sees.

   NO MEASURE, 2 okt. A ch measure, about 666px at 17ch, breaks headings
   over two lines that fit on one: the privacy policy needs 929px for "Sa
   hanterar vi personuppgifter." and the contact page 1148. The h1 takes
   the box it is in instead, which is a column on the pages that put it in
   one and the container on the pages that do not.

   text-wrap: balance still decides where it breaks when it has to break,
   so a heading too long for one line comes out in even lines rather than
   in a long one and a word. Section headings keep their measure: .display
   at 16ch and .display--sub at 20ch are unchanged. */
.display--page {
  max-width: none;
  font-size: clamp(2.375rem, 3.5vw + 0.75rem, 4.25rem);
  /* The design system's display weight, theme.json's display family at
     300. Set here and not on each caller: the page headings ran in two
     weights, 400 where they also carried .display, 300 where they did
     not. */
  font-weight: 300;
  text-wrap: balance;
}
/* The emphasis inside a page heading, at the hero's 500. Without it b and
   strong compute "bolder" than 300, which is 400: one step, hardly seen.
   .integration-heading b sets its own weight further down and wins on
   source order. */
.display--page :is(b, strong) {
  font-weight: 500;
}
.display--light {
  font-weight: 300;
}

/* ------------------------------------------------------------------
   Section label.

   The design system's SectionLabel: a small uppercase label over a full
   width rule. It is what separates one band from the next, which is why
   sections no longer carry a border-top of their own.

   NAMED AFTER THE COMPONENT, not "eyebrow". The design system lists a
   letterspaced uppercase label as something it does NOT want, on the old
   site's evidence, where it was the only typographic idea in a section
   and measured 2.48:1. Calling this one eyebrow reimported that argument
   every time the two were read side by side. This is the same device the
   system itself ships, so it carries the system's own name.

   The objection does not apply here, checked rather than assumed: the
   label measures 5.47:1 on the page ground and 5.14:1 on the light
   surface, and every section that uses it has real headings beneath it.

   The rule is graphite, not hairline. It is structure, not decoration,
   and hairline at 1.34:1 is too faint to read as a division.
   ------------------------------------------------------------------ */
.section-label,
.is-style-label,
.is-style-label-heading {
  margin: 0 0 clamp(32px, 4vw, 56px);
  padding-bottom: var(--wp--preset--spacing--40);
  border-bottom: 1px solid var(--wp--preset--color--graphite);
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  letter-spacing: 0.18em;
  text-transform: uppercase;
}
/* Same label without the rule, for use inside a panel. */
.section-label--bare {
  margin-bottom: 0;
  padding-bottom: 0;
  border-bottom: 0;
}

/* The label when it is also the section's heading, the block style
   "is-style-label-heading". At the component's own 12px that would put a
   heading below body text, which is the wrong way round however it is read.

   20px is the floor, not a design change: it is still the system's
   SectionLabel, still uppercase, still over its rule. The tracking comes
   down from 0.18em because 0.18em at 20px runs a longer label wider than
   the 360 viewport. */
.is-style-label-heading {
  font-size: 1.25rem;
  letter-spacing: 0.08em;
}

/* On a dark surface the body colour collapses to 2.75:1, which is within a
   quarter point of the 2.48:1 the design system rejected on the old site.
   The design system's SectionLabel has an inverse variant for exactly this;
   its soft on-dark ink measures 14.14:1. The rule under it follows. */
.section--dark :is(.section-label, .is-style-label, .is-style-label-heading),
/* The film hero is dark too. It carries its own background rather than
   the .section--dark class, so it needs naming here; without it the label
   and the lead come out body coloured on graphite, at 2.75:1. */
.section--hero .section-label,
.site-footer .section-label {
  color: var(--wp--preset--color--surface);
  border-bottom-color: var(--hairline-color-dark);
}

/* ------------------------------------------------------------------
   Mechanism diagram.

   A hub: four systems in, four out, through one centre that carries the
   Syncify mark. Thin lines on soft curves, which is v.1's rule for
   diagrams: continuity and direction, never right angles. The circles are
   the design's. The diagram language is not settled.

   The dash that travels along each path is .flow-diagram__flow, under
   "The dash that travels along a path" further down, because it belongs
   to the drawing and not to this figure.
   ------------------------------------------------------------------ */
.diagram {
  margin: clamp(40px, 5vw, 72px) 0 0;
}
/* The figure already carries the gap above, and .flow-fan carries one of
   its own for the page that uses it bare. Inside the figure that is the
   same distance twice. */
.diagram .flow-fan {
  margin-top: 0;
}
/* 16 AND NOT 12. A caption under a whole illustration, which is a bigger
   boundary than twelve pixels off the scale describes. */
.diagram__note {
  margin-top: var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--wp--preset--color--text-body);
}

/* ------------------------------------------------------------------
   Columns. Plain text columns, no card chrome. Used under the diagram.
   ------------------------------------------------------------------ */
.columns {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 260px), 1fr));
  gap: var(--wp--preset--spacing--65) clamp(32px, 5vw, 80px);
  margin-top: var(--stack-lg);
}
.columns__item h3 {
  margin: 0;
  font-size: clamp(1.25rem, 0.8vw + 0.8rem, 1.5625rem);
  line-height: 1.25;
  letter-spacing: -0.01em;
}
.columns__item p {
  max-width: 42ch;
  margin: var(--wp--preset--spacing--40) 0 0;
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
}

/* ------------------------------------------------------------------
   Ownership. Two bounded surfaces and a line between them, not a
   circle. The distinction is two owners and the boundary between them.

   The lines are still. [decision 24 Sep] Two pseudo elements rather than
   two borders, because the horizontal line belongs to the grid and the
   vertical one to the first panel, and a border on either would move with
   padding.
   ------------------------------------------------------------------ */
.ownership {
  position: relative;
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 320px), 1fr));
  margin-top: var(--stack-lg);
}

/* The horizontal line, above both panels. */
.ownership::before {
  content: "";
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 1px;
  background: var(--wp--preset--color--hairline);
}
.ownership__panel {
  padding: clamp(32px, 4vw, 56px) 0;
}
.ownership__panel h3 {
  margin: var(--wp--preset--spacing--45) 0 0;
  font-size: clamp(1.5rem, 1.2vw + 1rem, 2rem);
  font-weight: 400;
  line-height: 1.2;
  letter-spacing: -0.01em;
}
.ownership__panel p:not(.section-label) {
  max-width: 40ch;
  margin: var(--wp--preset--spacing--45) 0 0;
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
}
/* The dividing line, and the breathing room on either side of it. Only
   from the width where the panels actually sit side by side. */
@media (min-width: 768px) {
  .ownership__panel:first-child {
    position: relative;
    padding-inline-end: clamp(32px, 5vw, 80px);
  }
  .ownership__panel:last-child {
    padding-inline-start: clamp(32px, 5vw, 80px);
  }

  /* The vertical line between the panels. Only from the width where the
     panels actually sit side by side; stacked, there is nothing between
     them to divide. */
  .ownership__panel:first-child::after {
    content: "";
    position: absolute;
    top: 0;
    inset-inline-end: 0;
    width: 1px;
    height: 100%;
    background: var(--wp--preset--color--hairline);
  }
}

/* ------------------------------------------------------------------
   Fields.

   The theme's own form markup: the search form, and anything else the
   theme renders itself. Gravity Forms has its own block below.

   THE LINE IS TEXT-BODY, NOT HAIRLINE [Emilie 23 okt]. The design system's
   field line clears 3:1 against the field (WCAG 1.4.11): a field is a
   control, and its edge is how a reader finds it. The hairline is 1.4:1.
   ------------------------------------------------------------------ */
.field {
  width: 100%;
  min-height: var(--field-height);
  padding: 0 var(--field-pad-x);
  border: 1px solid var(--wp--preset--color--text-body);
  border-radius: var(--radius-button);
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
  font: inherit;
}
.field::placeholder {
  color: var(--wp--preset--color--text-body);
  opacity: 1;
}
.field:hover {
  border-color: var(--wp--preset--color--text-strong);
}
/* Focus as the design system draws it: the line goes graphite and doubles
   inward, so nothing around the field moves. The ring outside it is the
   theme's own, from the :focus-visible rule near the top. */
.field:focus {
  border-color: var(--wp--preset--color--text-strong);
  box-shadow: inset 0 0 0 1px var(--wp--preset--color--text-strong);
}

.search-form__label {
  display: block;
  margin-bottom: var(--field-label-gap);
  font-size: var(--wp--preset--font-size--brod-liten);
  font-weight: 500;
}
.search-form__row {
  display: flex;
  flex-wrap: wrap;
  gap: var(--field-gap);
  max-width: 34rem;
}
/* The field takes what is left; the button keeps its own width. Below the
   wrap they stack, and the button goes full width rather than sitting
   alone and undersized on its own line. */
.search-form__row .field {
  flex: 1 1 14rem;
}
.search-form__row .button {
  flex: 0 0 auto;
}

/* ------------------------------------------------------------------
   Gravity Forms [Emilie 23 okt].

   The design system's field, from the component library (Input,
   Textarea, FieldFrame, FormLayout): 48px high, 14px in from the edge, a
   13px label at weight 500 eight pixels above, fields 24px apart, a line
   that clears 3:1, and focus as a graphite line one pixel thicker. The
   button is the theme's primary button.

   THROUGH THE PLUGIN'S STYLE API, ONLY VARIABLES. Colours, radius, label
   and hint size come from the gform_default_styles filter in
   inc/forms.php; the rest is set here as Orbital's own custom properties.
   No rule reaches into the plugin's markup, so an update that moves its
   classes around does not move the form.

   TWO CLASSES, because the plugin's stylesheets load after this one and
   declare the same properties on one. Nothing here needs !important.
   ------------------------------------------------------------------ */
.gform_wrapper.gform-theme--orbital {
  --gf-font-family-base: inherit;
  --gf-ctrl-size-lg: var(--field-height);
  --gf-ctrl-padding-x: var(--field-pad-x);
  --gf-label-space-primary: var(--field-label-gap);
  --gf-ctrl-label-font-weight-primary: 500;
  --gf-ctrl-font-size: 15px;
  --gf-form-gap-y: 24px;
  --gf-ctrl-choice-size-lg: 20px;
  --gf-ctrl-shadow: none;

  /* Hover keeps the line; focus turns it graphite and adds a pixel. */
  --gf-ctrl-border-color-hover: var(--wp--preset--color--text-body);
  --gf-ctrl-border-color-focus: var(--wp--preset--color--text-strong);
  --gf-ctrl-outline-color-focus: var(--wp--preset--color--text-strong);
  --gf-ctrl-outline-width-focus: 1px;
  --gf-ctrl-outline-offset: 0;

  /* The required asterisk in body ink, not the plugin's red: a required
     field is not an error. */
  --gf-ctrl-label-color-req: var(--wp--preset--color--text-body);
  /* The asterisk straight after the word or the full stop, with no space
     before it [Emilie 17 nov]. The plugin pads the label's text by this
     much when an asterisk follows, 6px, on every label and the consent's
     sentence alike. */
  --gf-label-req-gap: 0;

  --gf-ctrl-checkbox-check-radius: 4px;

  /* The button a step closer than a field is to the next [Emilie 23 okt]. */
  --gf-form-footer-margin-y-start: var(--wp--preset--spacing--40);

  --gf-ctrl-btn-radius: var(--radius-button);
  --gf-ctrl-btn-padding-x-lg: 24px;
  --gf-ctrl-btn-shadow: none;
  --gf-ctrl-btn-bg-color-hover-primary: var(--wp--preset--color--graphite-deep);
  --gf-ctrl-btn-border-color-hover-primary: var(--wp--preset--color--graphite-deep);
}
/* The submit button's box, the same as .button's: spacing 30 above and
   below and a line height of 1.3 instead of the plugin's 0 and 1, so a
   label that wraps has air against the border. One line is still 48px,
   held by the plugin's min-height: two steps of 12 or less, 20.8 of line
   and the border fall short of it. Text-align is centre already.

   ON THE FOOT, NOT THE WRAPPER. The plugin reads the same two variables
   for every button in a form, the list field's small add and remove
   buttons among them, and those are not meant to grow. */
.gform_wrapper.gform-theme--orbital :is(.gform_footer, .gform_page_footer) {
  --gf-ctrl-btn-padding-y: var(--wp--preset--spacing--30);
  --gf-ctrl-btn-line-height: 1.3;
}

/* The required legend's paragraph, emptied in inc/forms.php. The plugin
   prints the paragraph all the same, and its 16px margin collapsed out of
   the empty heading and pushed the contact page's second form down. */
.gform_wrapper .gform_required_legend:empty {
  display: none;
}

/* ON A DARK BAND: the design system's inverse field. The about page's
   demo band and contact-info-dark put a form on graphite, where the
   light colours above would print graphite labels on graphite.

   ON THE BODY AND THE FOOT, NOT THE WRAPPER. The filter's colours sit on
   the wrapper under its id, which no class can out-rank; a custom
   property set on a child wins there by inheritance instead. Every
   derived value is set too (hover, focus, placeholder): the plugin
   resolves those on the wrapper, from the light colours, and they would
   otherwise come down unchanged. */
:is(.section--dark, .section--graphite, .section--graphite-deep) .gform_wrapper.gform-theme--orbital :is(.gform_body, .gform_footer) {
  --gf-ctrl-label-color-primary: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-label-color-secondary: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-label-color-req: var(--text-muted-on-dark);
  --gf-ctrl-desc-color: var(--text-muted-on-dark);

  --gf-ctrl-bg-color: var(--field-fill-on-dark);
  --gf-ctrl-bg-color-hover: var(--field-fill-on-dark);
  --gf-ctrl-bg-color-focus: var(--field-fill-on-dark);
  --gf-ctrl-color: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-color-hover: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-color-focus: var(--wp--preset--color--text-on-dark);
  /* Not the muted ink: on the field's lifted fill, about #3A454F, that
     measured 3.73:1. The pale hairline grey measures 7.28:1 and still
     sits visibly below the white of what the visitor types. */
  --gf-ctrl-placeholder-color: var(--wp--preset--color--hairline);

  --gf-ctrl-border-color: var(--field-line-on-dark);
  --gf-ctrl-border-color-hover: var(--field-line-on-dark);
  --gf-ctrl-border-color-focus: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-outline-color-focus: var(--wp--preset--color--text-on-dark);
  /* The check is drawn on the field's own fill, which stays translucent on
     graphite when ticked, so it takes the light ink. Graphite here left the
     tick invisible on the consent box. */
  --gf-ctrl-choice-check-color: var(--wp--preset--color--text-on-dark);
  --gf-ctrl-accent-color: var(--wp--preset--color--text-on-dark);

  --gf-ctrl-btn-bg-color-primary: var(--wp--preset--color--ground);
  --gf-ctrl-btn-border-color-primary: var(--wp--preset--color--ground);
  --gf-ctrl-btn-color-primary: var(--wp--preset--color--graphite);
  --gf-ctrl-btn-bg-color-hover-primary: var(--wp--preset--color--surface);
  --gf-ctrl-btn-border-color-hover-primary: var(--wp--preset--color--surface);
  --gf-ctrl-btn-color-hover-primary: var(--wp--preset--color--graphite);
  --gf-ctrl-btn-bg-color-focus-primary: var(--wp--preset--color--surface);
  --gf-ctrl-btn-color-focus-primary: var(--wp--preset--color--graphite);
}
/* The one rule here that is not a variable. theme.json colours every link
   graphite, and a link in the form (the consent's, say) would go with it,
   graphite on graphite. It takes the text's colour; the underline marks it. */
:is(.section--dark, .section--graphite, .section--graphite-deep) .gform_wrapper.gform-theme--orbital a {
  color: inherit;
}
/* Orbital takes the underline off every link in a form, theme.json's
   included. In the consent line the link is the same ink as the sentence
   around it, so without the line the policy reads as plain text. */
.gform_wrapper.gform-theme--orbital a {
  text-decoration: underline;
  text-underline-offset: 3px;
}

/* FOCUS ON THE LINK AND THE BUTTON: the theme's ring, not the field's
   line (WCAG 2.4.7) [16 nov]. The field focus above, 1px at offset 0 in
   graphite, is drawn on the button's own edge, graphite on graphite, and
   could not be seen. The plugin's reset unsets outline on every element in
   the form, which beats the theme's :focus-visible rule, since :where()
   weighs nothing, so the consent link had no ring at all.

   The button through the variables, set on the button itself so the dark
   band's colours on the foot do not reach it; --focus-ring already turns
   with the surface. The plugin draws it on :focus, so a click shows it
   too. The link has no variable, so it takes the rule. */
.gform_wrapper.gform-theme--orbital :is(.gform_footer, .gform_page_footer) :is(button, input[type="submit"], input[type="button"]) {
  --gf-ctrl-outline-color-focus: var(--focus-ring);
  --gf-ctrl-outline-width-focus: 2px;
  --gf-ctrl-outline-offset: 2px;
}
.gform_wrapper.gform-theme--orbital a:focus-visible {
  outline: 2px solid var(--focus-ring);
  outline-offset: 2px;
}

/* ------------------------------------------------------------------
   Floating labels `[Emilie 17 nov]`.

   The design system's floating label, outline variant (handoff
   "Formulär med floating labels", 1b). The label lies in the field at
   rest and moves into its top edge on focus, value or autofill.
   inc/forms.php marks the fields with .gfield--floating, shows their
   label and gives them a placeholder of one space.

   NO SCRIPT. The field's state is read with :has(): focus, a value
   (:placeholder-shown goes false once anything is typed, which is why
   the placeholder is a space) and autofill. Each sets --field-float to
   1, and the label, the tab and their transitions follow that one number.

   15px AT REST, NOT THE DESIGN SYSTEM'S 13. The label at rest stands
   where the visitor's text will, and the field's text is 15px. Moved up
   it is scaled by 0.8, which lands on 12px, the page's floor; 13 would
   have landed on 10.4.

   THE LABEL CARRIES THE FIELD'S FILL OVER THE SURFACE behind the form,
   at rest too, where it cannot be seen against the field. That is what
   hides the border behind the label through the whole movement, also on
   the way back down. The surface is --field-surface, set beside the
   background of every band a form stands on; a band that gets a form
   and a new colour needs it too, or the label shows a box of the ground.

   THE TAB, where the surface is not the field's colour (--field-tab, on
   .section--surface): the border follows round the raised label instead
   of breaking under it. Drawn as the label's ::after, so it takes the
   label's width with no measuring. It is scaled with the label, so its
   numbers are the handoff's divided by 0.8: 1.25px of border is 1px on
   screen, 10px of radius is 8. On a dark band there is no tab and the
   border only breaks behind the label.

   A MESSAGE STANDS UNDER THE FIELD, whatever the form says. The label
   is placed from the top of the field, so a validation message above
   (form 7 has that setting) would put the label over the message.
   ------------------------------------------------------------------ */
.gform_wrapper.gform-theme--orbital .gfield--floating {
  --field-float: 0;
  --field-label-ink: var(--wp--preset--color--text-body);
  --field-label-ink-active: var(--wp--preset--color--text-strong);
  --field-label-fill: linear-gradient(var(--gf-ctrl-bg-color), var(--gf-ctrl-bg-color)), var(--field-surface, var(--wp--preset--color--ground));
  position: relative;
  display: flex;
  flex-direction: column;
}
/* On a dark band the label at rest is the hairline grey and not the
   muted ink: on the field's lifted fill the muted ink measured 3.73:1,
   the hairline grey 7.28:1 (see the dark band's placeholder above). */
:is(.section--dark, .section--graphite, .section--graphite-deep) .gform_wrapper.gform-theme--orbital .gfield--floating {
  --field-label-ink: var(--wp--preset--color--hairline);
  --field-label-ink-active: var(--wp--preset--color--text-on-dark);
}
.gform_wrapper.gform-theme--orbital .gfield--floating > :not(.gfield_label, .ginput_container) {
  order: 1;
}

/* Four rules and not one list: :has() with a pseudo-class a browser does
   not know drops the whole rule, and :autofill and :-webkit-autofill are
   each unknown somewhere. Chrome matches -webkit-autofill already while
   the pointer rests on a suggestion, before anything is chosen, so the
   label is out of the way of the preview text. A select always has a
   value. */
.gform_wrapper.gform-theme--orbital .gfield--floating:has(:is(input, textarea, select):focus),
.gform_wrapper.gform-theme--orbital .gfield--floating:has(:is(input, textarea):not(:placeholder-shown)),
.gform_wrapper.gform-theme--orbital .gfield--floating.gfield--type-select {
  --field-float: 1;
}
.gform_wrapper.gform-theme--orbital .gfield--floating:has(input:-webkit-autofill) {
  --field-float: 1;
}
.gform_wrapper.gform-theme--orbital .gfield--floating:has(input:autofill) {
  --field-float: 1;
}

/* At rest: 10px in with 4px of padding puts the words on the field's
   own 14px, and 14px down centres the 20px line in the 48px field.
   Raised: 7.5px up centres the 16px label (20 at 0.8) on the 1px border. */
.gform_wrapper.gform-theme--orbital .gfield--floating > .gfield_label {
  position: absolute;
  z-index: 1;
  top: 0;
  left: calc(var(--field-pad-x) - 4px);
  max-width: calc(100% - 2 * var(--field-pad-x));
  margin: 0;
  padding: 0 4px;
  border-radius: 4px;
  background: var(--field-label-fill);
  color: var(--field-label-ink);
  font-size: 15px;
  font-weight: 400;
  line-height: 20px;
  white-space: nowrap;
  pointer-events: none;
  transform-origin: 0 0;
  transform: translateY(calc(14px - 21.5px * var(--field-float))) scale(calc(1 - 0.2 * var(--field-float)));
  transition: transform var(--dur-hover) var(--ease), color var(--dur-hover) var(--ease);
}
.gform_wrapper.gform-theme--orbital .gfield--floating:has(:is(input, textarea, select):focus) > .gfield_label,
.gform_wrapper.gform-theme--orbital .gfield--floating.gfield_error > .gfield_label {
  color: var(--field-label-ink-active);
}
/* The tab in the label's own, scaled, coordinates: 11px above the field
   and down to the inside of its border on screen, 2px wider than the
   label on each side. Behind the label's words (z-index -1 in the
   label's own stacking context, which the transform makes). */
.gform_wrapper.gform-theme--orbital .gfield--floating > .gfield_label::after {
  content: "";
  position: absolute;
  z-index: -1;
  top: -4.375px;
  right: -2.5px;
  left: -2.5px;
  height: 15px;
  box-sizing: border-box;
  border: 1.25px solid var(--gf-ctrl-border-color);
  border-bottom: 0;
  border-radius: 10px 10px 0 0;
  background: var(--field-label-fill);
  opacity: calc(var(--field-tab, 0) * var(--field-float));
  transition: opacity var(--dur-hover) var(--ease), border-color var(--dur-hover) var(--ease);
}
.gform_wrapper.gform-theme--orbital .gfield--floating:has(:is(input, textarea, select):focus) > .gfield_label::after {
  border-width: 2.5px;
  border-color: var(--gf-ctrl-border-color-focus);
}
.gform_wrapper.gform-theme--orbital .gfield--floating.gfield_error > .gfield_label::after {
  border-color: var(--gf-ctrl-border-color-error);
}

/* The message box's first line on the label's line at rest, not the
   plugin's padding, which set it lower. */
.gform_wrapper.gform-theme--orbital .gfield--floating textarea {
  padding-top: 12px;
}

/* The browser's autofill colour would take the field's fill, and the
   label's fill would then stand out as a box of the old colour. The
   transition holds the colour back for as long as anyone stays. Two
   rules, for the reason above. */
.gform_wrapper.gform-theme--orbital .gfield--floating input:-webkit-autofill {
  transition: background-color 0s 600000s, color 0s 600000s;
  -webkit-text-fill-color: var(--gf-ctrl-color);
  caret-color: var(--gf-ctrl-color);
}
.gform_wrapper.gform-theme--orbital .gfield--floating input:autofill {
  transition: background-color 0s 600000s, color 0s 600000s;
  -webkit-text-fill-color: var(--gf-ctrl-color);
  caret-color: var(--gf-ctrl-color);
}

@media (prefers-reduced-motion: reduce) {
  .gform_wrapper.gform-theme--orbital .gfield--floating > .gfield_label,
  .gform_wrapper.gform-theme--orbital .gfield--floating > .gfield_label::after {
    transition: none;
  }
}

/* THE FALLBACK: LABELS ABOVE. assets/js/form-labels.js sets the class on
   a form where one floating label is wider than its field, and every
   label in that form then stands above its field, as the theme's label
   did before: 13px at weight 500, 8px over the field, in the label ink. */
.gform_wrapper.gform_wrapper--labels-above .gfield--floating > .gfield_label {
  position: static;
  max-width: none;
  margin-bottom: var(--field-label-gap);
  padding: 0;
  background: none;
  color: var(--field-label-ink-active);
  font-size: 13px;
  font-weight: 500;
  white-space: normal;
  transform: none;
  transition: none;
}
.gform_wrapper.gform_wrapper--labels-above .gfield--floating > .gfield_label::after {
  content: none;
}

/* Two columns with a hairline between them, for the text and image
   pattern. Core's columns block gives the split; the line and the
   breathing room around it are the theme's. */
@media (min-width: 768px) {
  .text-and-image > .wp-block-column + .wp-block-column {
    padding-inline-start: clamp(32px, 5vw, 80px);
    border-inline-start: 1px solid var(--wp--preset--color--hairline);
  }
}

/* ------------------------------------------------------------------
   Partner band.

   A row of logotypes gliding sideways at a constant rate. Linear, never
   accelerating, never pausing: the design system's movement principle is
   an even pace that does not ask for attention.

   THE SEAM. The list is rendered twice and the track travels from 0 to
   -50% of its own width. At the end of a pass the frame is identical to
   the frame at the start, so the loop cannot be seen to restart. This
   only holds while both passes are the same width, which is why the
   duplicate is a copy and not a subset.

   Settings arrive as custom properties from the partial, so one
   stylesheet serves every instance.
   ------------------------------------------------------------------ */
.partner-band {
  --band-duration: 100s;
  --band-gap: 32px;
  --band-row: 56px;
  --band-fade: 160px;

  position: relative;
  overflow: hidden;
  /* The track is thousands of pixels wide by design. Without this its
     width is still counted when an ancestor is sized by its content, and
     it was: it is what pushed main to 2888. inline-size containment
     makes the band's width independent of what is inside it. */
  contain: inline-size;

  /* There is a SECOND .partner-band rule, under "The edges" below. It
     carries the mask that fades both ends, and it lives with the comment
     that explains it rather than here. Editing the band means reading
     both. */
}

/* Stacked rows need air between them, and the rule is on the sibling so
   any number of rows spaces itself without a wrapper or a second class. */
.partner-band + .partner-band {
  margin-top: var(--wp--preset--spacing--40);
}

.partner-band__track {
  display: flex;
  width: max-content;
  animation: syncify-band var(--band-duration) linear infinite;
}
.partner-band--reverse .partner-band__track {
  animation-direction: reverse;
}

.partner-band__run {
  display: flex;
  align-items: center;
}

.partner-band__cell {
  display: flex;
  align-items: center;
  justify-content: center;
  height: var(--band-row);
  padding-inline: var(--band-gap);
}

/* The height comes from the element, set per logotype: their optical
   weight differs enough that one height makes some shout and others
   disappear. Everything else about the mark is shared. */
.partner-band__logo {
  display: block;
  width: auto;
  /* The cap is printed on the band by inc/partner-band.php, which also caps
     the width attribute at the same number so the box the browser reserves
     before the file loads is the box it keeps. Change it there, not here;
     the literal is the same value and exists only for a mark drawn outside
     a band, which nothing renders today. */
  max-width: var(--band-logo-max, 220px);
  object-fit: contain;
}

@keyframes syncify-band {
  from { transform: translateX(0); }
  to   { transform: translateX(-50%); }
}

/* The edges. The band itself fades out towards both ends so marks
   dissolve instead of being cut at the frame.

   A mask on the band, not a pair of overlays painted on top of it. The
   overlays depended on paint order: they had to land above the moving
   track, and in Firefox the text inside the track came out above them, so
   the marks faded while their labels were cut off sharp. A mask is applied
   to the band's own rendering, so there is no order to get wrong, and it
   works on any surface without being told what colour is behind it.

   The width is capped as a share of the band as well as in pixels: at
   360px the specified 160 on each side would cover the whole row and
   leave nothing but fade. */
.partner-band {
  --band-fade-edge: min(var(--band-fade), 18%);
  -webkit-mask-image: linear-gradient(
    90deg,
    transparent,
    #000 var(--band-fade-edge),
    #000 calc(100% - var(--band-fade-edge)),
    transparent
  );
  mask-image: linear-gradient(
    90deg,
    transparent,
    #000 var(--band-fade-edge),
    #000 calc(100% - var(--band-fade-edge)),
    transparent
  );
}

/* Standing still. The movement stops and the first logotypes stay where
   they are; the duplicate goes, since its only job was the seam. The
   fades stay, so the row still ends softly rather than being chopped.

   animation-timeline is not involved here, but the global reduced motion
   block would only shorten this animation rather than stop it, and a
   marquee at 0.01ms is a blur. It is turned off outright. */
@media (prefers-reduced-motion: reduce) {
  .partner-band__track {
    width: 100%;
    animation: none;
  }
  .partner-band__run[aria-hidden="true"] {
    display: none;
  }
}

/* ------------------------------------------------------------------
   Flow row.

   The design is a carousel with prev and next buttons. Those need
   JavaScript, so this is a native scroller with snapping: same card
   size, same gap, same rhythm, and it works with a keyboard, with a
   touch screen and with scripting off.
   ------------------------------------------------------------------ */
/* The flows section closes on the flow row's controls, not on prose, and
   the controls already carry air under the cards. Its bottom padding is
   therefore a step down from the section token. Together with the shortened
   top on .section--contact the boundary is one ordinary padding rather than
   two, which is what the doubled space at the foot of this section was.
   [decision 28 Sep]

   THE INTEGRATIONS SECTION ENDS THE SAME WAY, on the partner band, and
   had the same doubled space: 224px between the band and the flows
   label at 1440, against 135 under the flow
   row [measured 12 okt]. It
   read as missing content. Same step down at its foot, and the flows label
   takes the contact section's shortened top, so the two boundaries are one
   measure. Below about 800px the section token is already at its 64px
   floor and the change is a few pixels. */
.section--integrations,
.section--flows {
  padding-bottom: var(--wp--preset--spacing--80);
}
/* THE CATEGORY CHIPS ARE THE FALLBACK FOR THE BAND [Emilie 14 nov]. They
   say which kinds of system are covered only while no approved logotype
   can be drawn; once the band is there the marks say it, and the chips
   are hidden. acf/partner-band renders nothing at all without an approved
   mark, so the band's presence is the whole condition and no PHP has to
   know about the chips. */
.section--integrations:has(.partner-band) .integration-categories {
  display: none;
}
/* The band's slot stands a step further from the lead than the block gap
   [Emilie 16 nov]. One rule for the band and the chips that hold its
   place, so the slot does not move when the first logotype is approved. */
.section--integrations :is(.partner-band, .integration-categories) {
  margin-top: var(--wp--preset--spacing--65);
}

.section--integrations + .section--flows {
  padding-top: var(--wp--preset--spacing--70);
}
/* THE FLOWS HEADING RUNS ON ONE LINE ON A WIDE SCREEN [Emilie 11 nov].
   "Så löser vi det mellan era system" is 33 characters against
   .display--sub's 20ch cap, so it broke in two with most of the container
   empty beside it. From 1024 the line fits the container at the clamp's
   size; below that the cap and the balanced break stay. */
@media (min-width: 1024px) {
  .section--flows .display--sub {
    max-width: none;
  }
}
/* The heading over the short form takes the container too [Emilie 16
   nov], at every width: balance still decides where it breaks. */
.section--contact:has(.form-slot--inline) .display--sub {
  max-width: none;
}

/* The head: the two step buttons and the position counter, UNDER the row
   and pushed right, with the counter under the buttons. [decision 28 Sep]

   It reads as one control rather than a label at one end of the section and
   two buttons at the other, and it puts the counter next to the thing that
   changes it. The DOM order follows the visual order, so a keyboard reaches
   the cards first and the controls after, which is the order they are in.

   Right aligned with align-items rather than text-align, because the counter
   and the button pair are different widths and both have to end on the same
   pixel. */
.flow-head {
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  gap: var(--wp--preset--spacing--30);
  padding-block: var(--wp--preset--spacing--50) 0;
  font-size: var(--wp--preset--font-size--brod-liten);
}
.flow-head__count {
  margin: 0;
  font-weight: 500;
  /* Tabular figures so the line does not jog sideways as the numbers change
     under the buttons. */
  font-variant-numeric: tabular-nums;
}
.flow-head__nav {
  display: flex;
  gap: var(--wp--preset--spacing--20);
}
/* Real buttons: they act on the page, they do not navigate. Square enough
   to hit on a touch screen, which the design's 34px is not. */
.flow-step {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  padding: 0;
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-button);
  background: transparent;
  color: var(--wp--preset--color--text-strong);
  font: inherit;
  font-size: 18px;
  line-height: 1;
  cursor: pointer;
  transition: background var(--dur-hover) var(--ease), border-color var(--dur-hover) var(--ease);
}
.flow-step:hover {
  background: var(--wp--preset--color--surface);
  border-color: var(--wp--preset--color--graphite);
}
.flow-step[disabled] {
  opacity: 0.35;
  cursor: default;
}
.flow-step[disabled]:hover {
  background: transparent;
  border-color: var(--wp--preset--color--hairline);
}

.flow-row {
  display: flex;
  gap: var(--wp--preset--spacing--40);
  /* ROOM FOR THE SHADOW, AND NOTHING MOVES [7 okt]. overflow-x: auto
     forces overflow-y to auto as well, so this box clips what hangs
     outside it, and the card shadow hung 16px below and 6px to each side.
     The padding is that room, and the negative margin gives it back, so
     the first card still starts on the container's edge and the row is as
     wide as it was. Measured off the shadow: 10 + 24 - 6 downwards.

     THE 6px ON TOP IS THE FOCUS RING [7 okt], not the shadow, which hangs
     nothing above the card. The ring is 2px at an offset of 4, so it needs
     exactly that much or the top of it is cut off on a card reached by
     tabbing. The negative margin gives those 6px back as well. */
  margin: -6px -8px 0;
  padding: 6px var(--wp--preset--spacing--20) var(--wp--preset--spacing--45);
  list-style: none;
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  /* The snapport has to start where the padding ends, or the row snaps to
     a position 6px off and the first card hangs into the gutter. Measured
     at 1440: scrollLeft settled on 6 and the card stood at 42 against the
     container's 48. With this it is 0 and 48. */
  scroll-padding-inline: 8px;
  overscroll-behavior-x: contain;
  scroll-behavior: smooth;
  /* Same reason as the partner band: five cards at up to 300px each
     must never be allowed to size anything above this row. */
  contain: inline-size;
  /* The step buttons are the affordance here, so the bar is not needed and
     the design does not show one. The row still scrolls by touch, wheel and
     keyboard. */
  scrollbar-width: none;
}
.flow-row::-webkit-scrollbar {
  display: none;
}

.flow-card {
  display: flex;
  flex-direction: column;
  flex: 0 0 clamp(240px, 21vw, 300px);
  /* NO min-height. A fixed floor leaves the shortest card with empty space
     under its last line. The row is a flex row and stretches by default,
     so the tallest card sets the height and the rest follow it.

     The border, the radius and the shadow are the shared card rule; see
     "A LITTLE LIFT". Only what is this card's own is left here. */
  scroll-snap-align: start;
  /* The anchor in the title covers the card; see below. */
  position: relative;
}
/* THE SAME CARD IN A GRID [Emilie 13 okt]. The four system categories on
   the platform page asked to look like the front page's scenarios. They
   are a feature grid in the markup, so the modifier draws them as flow
   cards: these three rules and the shared card rule under "A LITTLE LIFT"
   name both, and a change to the card reaches both. The gap between them
   sits with the feature grid's own, further down. */
.flow-card,
.feature-grid--cards > .feature-col {
  padding: var(--wp--preset--spacing--50) var(--wp--preset--spacing--50) var(--wp--preset--spacing--45);
}
.flow-card__title,
.feature-grid--cards .feature-col__title {
  margin: 0;
  font-size: 20px;
  font-weight: 400;
  line-height: 1.25;
  letter-spacing: -0.01em;
}
.flow-card p,
.feature-grid--cards .feature-col__text {
  margin: var(--wp--preset--spacing--40) 0 0;
  font-size: 13px;
  line-height: 1.55;
  color: var(--wp--preset--color--text-body);
}
/* THE CARD IS A LINK [Emilie 7 okt], the same way .media-card is one:
   the anchor lives in the title and an ::after stretches it over the whole
   card. One link with the article's own name in it, not a box with an
   arrow in the corner; a screen reader hears what it leads to.

   NO FIELD AND NO NEW CONTRACT. The editor selects the title and adds the
   link with the ordinary rich text control. acf/flow-card stays a frame
   without fields, which is what CLAUDE.md asks of the frames, and the
   frozen markup on the front page needs no migration: the anchor goes in
   where the words already are.

   A CARD WITHOUT A LINK IS STILL A CARD. Everything here hangs off the
   anchor, so a title that carries none renders as a plain card: no
   pointer, no hover, no hit area that does nothing.

   NO ARROW BOX at the foot of the card. It makes every card look like a
   link whether or not it is one, and an aria-hidden arrow tells a screen
   reader user nothing at all. */
.flow-card__title a {
  color: inherit;
  text-decoration: none;
}
/* The hit area is the card, and the focus ring follows it rather than the
   two or three words of the title. */
.flow-card__title a::after {
  content: "";
  position: absolute;
  inset: 0;
  border-radius: var(--radius-card);
}
.flow-card__title a:focus-visible {
  outline: none;
}
.flow-card__title a:focus-visible::after {
  outline: 2px solid var(--focus-ring);
  outline-offset: 4px;
}
/* The whole card answers the pointer, so the title is what shows it. */
.flow-card:has(.flow-card__title a:hover) .flow-card__title {
  text-decoration: underline;
  text-underline-offset: 4px;
}
/* THE ARROW BESIDE THE TITLE [Emilie 15 nov], so the cards show that they
   are links; a button at the foot was tried the same day and dropped. It
   hangs off the anchor, so a card without a link still gets none. The mask
   is shared with "Med pil" further up. The title's own ::after, since the
   anchor's is the hit area.

   THE ARROW NEVER STANDS ALONE ON A LINE. An inline-block may break from
   the word before it, and on a phone it did, under "Order till betalning".
   So it is an inline box holding a word joiner (U+2060), which forbids the
   break, and the arrow is drawn into its left padding by the mask. The
   joiner has no width and no sound. */
.flow-card__title:has(a)::after {
  content: "\2060";
  display: inline;
  padding-left: 1.25em;
  -webkit-mask-position: right center;
  mask-position: right center;
  -webkit-mask-size: 0.9em;
  mask-size: 0.9em;
}

/* ------------------------------------------------------------------
   Contact.

   Light, and it stays light all the way down. The boundary to the footer
   is an edge, the same as every other boundary on the page, with a small
   ribbon rising out of it. On the flat ground body colour holds at 5.47:1
   and a paragraph is as safe here as anywhere.
   ------------------------------------------------------------------ */
.section--contact {
  position: relative;
  /* THE TOP IS SHORTER THAN A SECTION PADDING. [decision 28 Sep]

     Every other boundary on the page is two full paddings. Here that
     leaves 316px of ground between the last flow card and this heading at
     1440: the section above ends in the flow row's own controls, which
     already give the cards air beneath them, so a second full padding
     counts it twice.

     A spacing token rather than a fraction of the section token, so it is a
     step on the scale and not a number derived from another number. The
     bottom is the ordinary section padding. */
  padding-block: var(--wp--preset--spacing--70) var(--section-pad);
  overflow: hidden;
}
/* A SMALL RIBBON RISING OUT OF THE FOOTER [Emilie 8 okt].

   THE BAND IS THE COMPONENT, NOT THE PAGE. .section--contact is the closing
   band on six pages: the front page, integrationer, processer-erp-crm,
   ekonomisk-avstamning, integrationsplattform and order-till-betalning.
   One rule, so the six cannot drift apart; checked on all six.

   THE BOX SITS ON THE BAND'S BOTTOM EDGE, which is where the footer starts.
   Whatever the window shows therefore ends on that boundary, and an end on
   a boundary needs no fading: it reads as the figure carrying on behind the
   footer. That is the whole idea of it.

   THE TOP IS THE FIGURE'S OWN START [Emilie 14 okt], so it needs no
   fading either. The window is the head of the file, where the ribbon
   begins by itself on empty ground: the first ink is 2.7 per cent down
   flow.webp and 2.8 down the dark and graphite files, measured. A figure
   that stops on a straight edge in open space reads as broken; a figure
   that starts there does not.

   MATTED ON WHITE, so flow.webp and not one of the two dark files, at the
   0.55 that the colourway note further down measured as the only one a
   paragraph can sit on. No paragraph sits on this one in any case: the
   content is lifted above it by the rule below.

   IT KEEPS WELL CLEAR OF THE WORDS. Measured at the band's own widths, the
   room to the right of the heading and the buttons is 786px at 1440, 604
   at 1200, 435 at 1024 and 190 at 768, against a figure that is at most
   140 wide. Below 768 the buttons go full width and there is no room left,
   so the figure goes; see the media query under the rule.

   THE DARK CLOSING BAND TAKES THE SAME DEVICE [Emilie 8 okt]. Two pages end
   on graphite instead of on the page's white: erp-byte and om-oss.
   Everything about the figure is shared except the file and how
   strongly it is laid on: the matte is baked into the file, so a band of
   another colour takes another file, never another opacity on the same one.
   flow.webp is matted on white, flow-dark.webp on graphite.

   WRITTEN AS THE CONDITION, NOT AS A CLASS PER PAGE. The file already says
   which band this is, under "AND THE LAST DARK BAND ON A PAGE TAKES IT
   WITHOUT ASKING": a dark band that is the last child sits straight on the
   footer, and that is exactly the band this figure can rise out of. A dark
   band in the middle of a page has no footer under it and gets nothing.

   EXCEPT WHERE A LOGOTYPE GRID IS. A band that ends in the customer
   logotype grid has no room: the figure starts at 1195 and such a grid runs
   to 1362, so it would land on the marks. Measured at five widths, the
   margin was negative at every one, which is why this is an exclusion and
   not a tuning.

   NO BAND HAS ONE TODAY. The rule stays because the grid is coming back as
   an ACF block, and then it will be right without anyone remembering this.

   Those bands were static and did not clip. The light one already carries
   both, higher up where its padding is set; these needed them. */
:is(.site-main, .site-main > article) > .section--dark:last-child:not(:has(.logo-grid)) {
  position: relative;
  overflow: hidden;
}
.section--contact::before,
:is(.site-main, .site-main > article) > .section--dark:last-child:not(:has(.logo-grid))::before {
  content: "";
  position: absolute;
  z-index: 0;
  right: calc(var(--outside-container) + clamp(24px, 6vw, 120px));
  width: clamp(110px, 11vw, 170px);
  /* LEANS TO THE RIGHT [Emilie 14 okt], turned about the middle of its
     foot so only the top moves.

     THE FOOT IS SUNK 40px BELOW THE BAND, and both heights below add the
     same 40, so the figure rises exactly as far as it did upright. Turned
     on the edge itself, the box's bottom tilts with it and its left corner
     lifts, up to 18px at the widest, which showed as a slanted cut above
     the footer. Sunk, the band's overflow clips that edge out of sight. */
  bottom: -40px;
  transform: rotate(12deg);
  transform-origin: 50% 100%;
  pointer-events: none;
}
/* THE HEAD OF THE FILE, center top. At these sizes cover shows the top 15
   to 19 per cent of it: the start, and the ink thickening to its full
   width toward the footer. Both bands take the same crop: it is the same
   figure. The 40px is the sunk foot, see above: the visible rise is
   unchanged. */
.section--contact::before {
  height: calc(clamp(170px, 23vw, 320px) + 40px);
  /* ?v=2 on every flow file [26 okt]: the transparent files kept the old
     names, and a browser holding the matted ones drew their white box. */
  background: url("assets/media/flow.webp?v=2") center top / cover no-repeat;
  opacity: 0.8;
}
/* THE GRAPHITE RIBBON, ON INTEGRATIONER ONLY [Emilie 12 okt].

   THE FOURTH FILE, AND IT BREAKS THE NAMING. flow-dark and flow-deep are
   named for the GROUND they are matted on, graphite and graphite deep.
   This one is matted on WHITE like flow.webp and differs in its INK, which
   is graphite instead of cyan. Do not reach for flow-dark here: measured,
   its corner pixel is rgb(44, 53, 69) at full alpha, so on this white band
   it paints a graphite rectangle rather than a ribbon.

   Made from Marknad/flodesslingor/flodesslinga-grafit.png, which is the
   source set and carries a real alpha channel, 72 per cent transparent.
   Laid on white and written out at 440 wide to match the other three:
   15 960 bytes against flow.webp's 16 164. Keeping the alpha instead would
   have cost 202 kB, which is what the baked matte buys.

   A CLASS AND NOT A CONDITION, which is the exception to the rule above.
   Nothing about this band distinguishes it from the five other pages that
   end on .section--contact; it is a choice about one page, so it is said
   as a choice. Equal weight to the rule above, so it must stay after it. */
.section--ribbon-graphite::before {
  background-image: url("assets/media/flow-graphite.webp?v=2");
}
/* SHORTER, BECAUSE THE DARK BANDS ARE SHORTER OR BUSIER than the light
   one, and the light band's 320 would fill most of a short band. */
:is(.site-main, .site-main > article) > .section--dark:last-child:not(:has(.logo-grid))::before {
  height: calc(clamp(140px, 17vw, 240px) + 40px);
  background: url("assets/media/flow-dark.webp?v=2") center top / cover no-repeat;
  opacity: 0.6;
}
/* The words stand above the figure on every one of these bands. */
:is(.site-main, .site-main > article) > .section--dark:last-child > .container {
  position: relative;
  z-index: 1;
}
/* 1020, WHICH IS WHERE EVERY OTHER FIGURE IN THIS THEME GOES, and here it
   is erp-byte's closing band that sets it. The figure starts at a fixed
   distance from the right edge, so the room it needs is the room the words
   leave: measured on that band, the margin between the last word and the
   figure is 432px at 1440, 286 at 1200, 187 at 1024, 98 at 900 and minus 21
   at 768. It stops clearing somewhere under 900.

   ONE LINE FOR ALL THREE BANDS RATHER THAN ONE PER BAND. The light band's
   own numbers would have let it stand down to 768, and that range is the
   price of having a single rule. Eight other decorative figures already go
   at 1020; a ninth number would have to be remembered. */
@media (max-width: 1020px) {
  .section--contact::before,
  :is(.site-main, .site-main > article) > .section--dark:last-child::before {
    display: none;
  }
}

/* The words stand above the ribbon. */
.section--contact > .container {
  position: relative;
  z-index: 1;
}

.note,
.is-style-note {
  margin-top: var(--wp--preset--spacing--60);
  padding: var(--wp--preset--spacing--40) var(--wp--preset--spacing--45);
  border-left: 2px solid var(--wp--preset--color--graphic);
  background: var(--wp--preset--color--ground);
  font-size: var(--wp--preset--font-size--brod-liten);
}

/* ------------------------------------------------------------------
   Chip.

   A small label on a light surface. Not a button and not a link: it
   states a category, it does not do anything, so it has no hover, no
   focus ring and no cursor change.

   Two uses: the flow chip on a media card ("ERP till fakturering") and the
   status chip under a trust item ("Pågår"), which is outlined and set in
   the micro label style. The status chip is what the design system's
   inventory calls Status.

   The measurements are the ones read off the design system's own
   rendering at 1280 [24 Sep]. Keep this the only definition of .chip:
   two definitions of one class is one of them silently losing.
   ------------------------------------------------------------------ */
.chip {
  display: inline-flex;
  align-items: center;
  min-height: 28px;
  margin: 0;
  padding: 0 var(--wp--preset--spacing--30);
  border-radius: var(--radius-button);
  background: var(--wp--preset--color--surface);
  color: var(--wp--preset--color--text-strong);
  font-size: var(--wp--preset--font-size--brod-liten);
  font-weight: 500;
  line-height: 1;
  white-space: nowrap;
}
.chip--status {
  min-height: 26px;
  padding: 0 10px;
  /* The panel's rule and ink when it is in one, the page's otherwise. That
     is shorter than naming every dark surface it can sit on, and it was a
     missing name that put this chip at 2.75:1 on the hero: .section--dark
     had a rule for it and .section--hero did not. */
  border: 1px solid var(--panel-rule, var(--wp--preset--color--hairline));
  background: transparent;
  color: var(--panel-quiet, var(--wp--preset--color--text-body));
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.12em;
  text-transform: uppercase;
}
/* Not inside a panel, which is white on every surface. */
.section--dark .chip--status:not(.panel *) {
  border-color: var(--hairline-color-dark);
  color: var(--text-muted-on-dark);
}

/* ------------------------------------------------------------------
   Media card.

   A square picture with a metadata row: label, value, and an optional
   chip pushed to the right. With a link the whole card is the target,
   drawn from the value's link so the markup stays one anchor and the
   screen reader hears one name. From the design system's MediaCard, read
   at 1280: three cards of 390 with a 24 gap, 14 between picture and row.
   ------------------------------------------------------------------ */
.media-grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 260px), 1fr));
  gap: var(--wp--preset--spacing--50);
}
.media-grid > * {
  margin-block: 0;
}
.media-card {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 14px;
}
.media-card > * {
  margin-block: 0;
}
.media-card__image {
  margin: 0;
}
.media-card__image img {
  display: block;
  width: 100%;
  aspect-ratio: 1;
  object-fit: cover;
  border-radius: var(--radius-card);
}
/* An image block with no picture renders NOTHING on the page: core's
   render callback returns an empty string when there is no img. So a card
   without a picture yet draws its own square, in surface colour, so the
   row below sits where it will sit once the picture is chosen. A tint,
   never a picture that could reach production. */
.media-card:not(:has(img))::before {
  content: "";
  display: block;
  aspect-ratio: 1;
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--surface);
}
.media-card__meta {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 6px var(--wp--preset--spacing--20);
  font-size: 15px;
  line-height: 1.4;
}
.media-card__meta > * {
  margin: 0;
}
.media-card__label {
  color: var(--wp--preset--color--text-body);
}
.media-card__value {
  color: var(--wp--preset--color--text-strong);
}
/* The bar between label and value is drawn, not typed, so it cannot be
   left out or doubled and it disappears with the label. */
.media-card__label + .media-card__value::before {
  content: "|";
  margin-right: var(--wp--preset--spacing--20);
  color: var(--wp--preset--color--text-body);
  opacity: 0.7;
}
.media-card__value a {
  color: inherit;
  text-decoration: none;
}
/* The link's hit area is the whole card. The outline follows it. */
.media-card__value a::after {
  content: "";
  position: absolute;
  inset: 0;
  border-radius: var(--radius-card);
}
.media-card__value a:focus-visible {
  outline: none;
}
.media-card__value a:focus-visible::after {
  outline: 2px solid var(--focus-ring);
  outline-offset: 4px;
}
.media-card:has(.media-card__value a:hover) .media-card__value {
  text-decoration: underline;
}
.media-card__meta .chip {
  margin-left: auto;
}

/* ------------------------------------------------------------------
   Trust section.

   Section label with its rule, a display heading, a lead, then a row of
   items under a hairline, divided by vertical hairlines: an icon beside
   a title, a short text, and optionally the status chip. The dark variant
   is .section--dark on the section plus a footnote at the end.

   The icons are the theme's Heroicons paths as CSS masks, so a title takes
   its icon from one class and the icon takes the title's colour. Icons
   sit beside text and never alone, and never in the signal colour.

   THE PATHS ARE COPIES of file-text, lock, shield-check and clock in
   inc/icons.php, which is the source. Phone and mail are below them, for
   the contact page's ways to reach a human. A path changed there needs the same
   change in the data URI here. Adding an icon means adding a --icon rule
   below with the path from that file, never a new drawing.
   ------------------------------------------------------------------ */
.trust__grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 260px), 1fr));
  margin-top: var(--stack-lg);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.trust__grid > * {
  margin-block: 0;
}
.trust__item {
  padding: var(--wp--preset--spacing--65) var(--wp--preset--spacing--60) var(--wp--preset--spacing--65) 0;
}
.trust__item > * {
  margin-block: 0;
}
.trust__item + .trust__item {
  padding-left: var(--wp--preset--spacing--60);
  border-left: 1px solid var(--wp--preset--color--hairline);
}
/* Stacked, the divider between items is a rule above, not beside. */
@media (max-width: 767px) {
  .trust__item {
    padding: 28px 0;
  }
  .trust__item + .trust__item {
    padding-left: 0;
    border-left: 0;
    border-top: 1px solid var(--wp--preset--color--hairline);
  }
}
.trust__title {
  display: flex;
  /* THE ICON SITS ON THE FIRST LINE, not in the middle of the heading.
     align-items: center measures the whole flex line, so a heading that
     wrapped to two rows put its mark in the gap between them while a one
     row heading kept it beside the words. Four cards side by side then had
     their icons at two different heights.

     The mark is lowered onto the first line by ::before instead, see below. */
  align-items: flex-start;
  gap: 10px;
  margin: 0;
  /* rubrik-1, NOT rubrik-2: at 18px the heading would be smaller than the
     19px body text beside it. The class is fixed rather than the token
     raised [Emilie 30 sep]: rubrik-2 stays on the scale, where theme.json's
     h4 and the integrations and threecolumns block stylesheets read it.
     .split-row__title, .feature-col__title and .step-row__title follow this
     one. */
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 500;
  line-height: 1.3;
  letter-spacing: 0;
}
.trust__title[class*="has-icon-"]::before {
  content: "";
  flex: none;
  width: var(--icon-size, 18px);
  height: var(--icon-size, 18px);
  /* Centred on the first line box rather than on the element. 1lh is that
     box, whatever the line-height of whoever wears the class, so this does
     not have to be recalculated when a heading changes size. The link form
     is a single line, where this comes out the same as centring did. */
  margin-top: calc((1lh - var(--icon-size, 18px)) / 2);
  background-color: currentColor;
  -webkit-mask: var(--icon) center / contain no-repeat;
  mask: var(--icon) center / contain no-repeat;
}
.has-icon-file-text {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M19.5 14.25v-2.625a3.375 3.375 0 0 0-3.375-3.375h-1.5A1.125 1.125 0 0 1 13.5 7.125v-1.5a3.375 3.375 0 0 0-3.375-3.375H8.25m0 12.75h7.5m-7.5 3H12M10.5 2.25H5.625c-.621 0-1.125.504-1.125 1.125v17.25c0 .621.504 1.125 1.125 1.125h12.75c.621 0 1.125-.504 1.125-1.125V11.25a9 9 0 0 0-9-9Z'/%3E%3C/svg%3E");
}
/* A COPY of layers in inc/icons.php, which is the source, the same as the
   masks around it. The class was used on the platform page with no rule
   to match: a mask with no image masks nothing, so the pseudo element
   painted as an 18px square in the text colour. */
.has-icon-layers {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6.429 9.75 2.25 12l4.179 2.25m0-4.5 5.571 3 5.571-3m-11.142 0L2.25 7.5 12 2.25l9.75 5.25-4.179 2.25m0 0L21.75 12l-4.179 2.25m0 0 4.179 2.25L12 21.75 2.25 16.5l4.179-2.25m11.142 0-5.571 3-5.571-3'/%3E%3C/svg%3E");
}
.has-icon-lock {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M16.5 10.5V6.75a4.5 4.5 0 1 0-9 0v3.75m-.75 11.25h10.5a2.25 2.25 0 0 0 2.25-2.25v-6.75a2.25 2.25 0 0 0-2.25-2.25H6.75a2.25 2.25 0 0 0-2.25 2.25v6.75a2.25 2.25 0 0 0 2.25 2.25Z'/%3E%3C/svg%3E");
}
.has-icon-shield-check {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M9 12.75 11.25 15 15 9.75m-3-7.036A11.959 11.959 0 0 1 3.598 6 11.99 11.99 0 0 0 3 9.749c0 5.592 3.824 10.29 9 11.623 5.176-1.332 9-6.03 9-11.622 0-1.31-.21-2.571-.598-3.751h-.152c-3.196 0-6.1-1.248-8.25-3.285Z'/%3E%3C/svg%3E");
}
.has-icon-clock {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M12 6v6h4.5m4.5 0a9 9 0 1 1-18 0 9 9 0 0 1 18 0Z'/%3E%3C/svg%3E");
}
.has-icon-phone {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M2.25 6.75c0 8.284 6.716 15 15 15h2.25a2.25 2.25 0 0 0 2.25-2.25v-1.372c0-.516-.351-.966-.852-1.091l-4.423-1.106c-.44-.11-.902.055-1.173.417l-.97 1.293c-.282.376-.769.542-1.21.38a12.035 12.035 0 0 1-7.143-7.143c-.162-.441.004-.928.38-1.21l1.293-.97c.363-.271.527-.734.417-1.173L6.963 3.102a1.125 1.125 0 0 0-1.091-.852H4.5A2.25 2.25 0 0 0 2.25 4.5v2.25Z'/%3E%3C/svg%3E");
}
.has-icon-mail {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M21.75 6.75v10.5a2.25 2.25 0 0 1-2.25 2.25h-15a2.25 2.25 0 0 1-2.25-2.25V6.75m19.5 0A2.25 2.25 0 0 0 19.5 4.5h-15a2.25 2.25 0 0 0-2.25 2.25m19.5 0v.243a2.25 2.25 0 0 1-1.07 1.916l-7.5 4.615a2.25 2.25 0 0 1-2.36 0L3.32 8.91a2.25 2.25 0 0 1-1.07-1.916V6.75'/%3E%3C/svg%3E");
}
/* A COPY of building in inc/icons.php, which is the source. The company
   details' row in the contact card [Emilie 23 okt]. */
.has-icon-building {
  --icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M3.75 21h16.5M4.5 3h15M5.25 3v18m13.5-18v18M9 6.75h1.5m-1.5 3h1.5m-1.5 3h1.5m3-6H15m-1.5 3H15m-1.5 3H15M9 21v-3.375c0-.621.504-1.125 1.125-1.125h3.75c.621 0 1.125.504 1.125 1.125V21'/%3E%3C/svg%3E");
}
/* A COPY of check in inc/icons.php, which is the source. Change it there
   and here, the same as the .has-icon-* masks above. */
:root {
  --icon-check: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m4.5 12.75 6 6 9-13.5'/%3E%3C/svg%3E");
}
/* THE BODY TEXT STARTS AT ONE HEIGHT ACROSS THE CARDS. Without this it
   starts wherever the heading above it happens to end: on the platform page
   headings run to different numbers of lines, and a one line heading left
   its text 31px above the others.

   Subgrid, the same way the feature columns and the card grid do it further
   down. Three rows, because a card holds at most a heading, a text and a
   chip, and each of the three then gets a height all the cards share.

   No row-gap to reset here, unlike those two: this grid has no gap. The
   cards are divided by a border and their own padding, and the distance
   inside a card is each element's margin.

   Behind @supports: without subgrid the cards do what they did before,
   which is readable and merely unaligned. */
@supports (grid-template-rows: subgrid) {
  .trust__grid {
    grid-template-rows: auto auto auto;
  }
  .trust__item {
    display: grid;
    grid-row: span 3;
    grid-template-rows: subgrid;
  }
  /* A grid item stretches, and the chip is a shape that must not. It is
     inline-flex outside a grid and would otherwise run the card's width. */
  .trust__item .chip {
    justify-self: start;
  }
}
.trust__text {
  max-width: 36ch;
  margin-top: var(--wp--preset--spacing--30);
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
}
.trust__item .chip {
  margin-top: var(--wp--preset--spacing--40);
}
.trust__note {
  max-width: 62ch;
  margin-top: clamp(32px, 4vw, 56px);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
  color: var(--wp--preset--color--text-body);
}
.section--dark .trust__grid,
.section--dark .trust__item + .trust__item {
  border-color: var(--hairline-color-dark);
}
.section--dark .trust__title {
  color: var(--wp--preset--color--text-on-dark);
}
.section--dark :is(.lead, .is-style-lead),
.section--hero .lead,
.section--dark .trust__text,
.section--dark .trust__note {
  color: var(--text-muted-on-dark);
}

/* ------------------------------------------------------------------
   Contact page.

   The design system's kontakt template. An opening heading and lead,
   the section label, then two columns: the ways to reach a human plus
   the form on the left, the systems Syncify integrates with on the
   right. Below it the dark band with the short form.

   NEITHER FORM IS HERE. Both are Gravity Forms, rendered by the plugin
   with its own markup and its own stylesheet. What the theme owns is
   the hole they drop into: .form-slot sets the width and the space
   above it and nothing else. No rule below selects a GF class, so both
   ways out of README's open question are still open.

   The columns are auto-fit rather than a media query: the point at
   which the form and the system grid stop fitting side by side is a
   property of their own minimum width, not of a device.
   ------------------------------------------------------------------ */
/* The page heading, for any page whose h1 is in the content rather than in
   the template. .contact-heading was the first caller and keeps its name so
   the markup already published does not have to change.

   The size, the weight and the tracking are theme.json's h1 element style,
   which is the display-1 preset and is what the design draws. No measure,
   for the reason written beside .display--page: a page heading takes the
   box it is in. Balance keeps the last line from being a single word. */
.contact-heading,
.page-heading {
  text-wrap: balance;
}

/* The section label opens every other section on the site, so it has no top
   margin anywhere else. Here it comes AFTER the heading and the lead, and
   the rule under it divides the page. The gap is the section rhythm token,
   the same distance that separates one band from the next. */
.lead + .section-label {
  margin-top: var(--section-pad);
}

/* The flow ribbon behind the section.

   A pseudo element, not an img in the pattern: it is decoration, so it is
   not content an editor can select, move or delete, and there is no alt
   attribute anyone has to remember to leave empty.

   THE FILE HAS A WHITE BACKGROUND BAKED IN. The source is a palette PNG
   with an alpha channel, and the alpha was most of its weight: matted on
   white the same picture is 16 kB instead of 295. The trade is that this
   ribbon only works on the page ground. Put it on .section--surface or on a
   dark surface and it paints a white column. If a section like that ever
   needs it, ship a second file with alpha rather than swapping this one.

   The ribbon's right edge is tied to the content column, not to the
   window: it stands on the container's outer edge, moved out past it by
   1vw (never more than 64px), so on a window wider than the column it stays
   with the content instead of drifting towards the glass. Below 1440 the
   container's edge is the band's edge. It hangs out of the section at both
   ends and on the right, which is what overflow hidden is for.

   COVER AND CROPPED, NOT THE WHOLE FIGURE. The figure is nine times as
   tall as it is wide. Fitted whole it came out about 140px across, which
   read as a thread. The box is wide instead and cover scales the figure to
   that width, so what is on the page is the middle of it at size: the
   curve, the widening and the strands splitting, cropped top and bottom.
   THE 10% IS THE TOP EDGE. With the crop centred the figure was cut at a
   quarter of its length and the top of the ribbon was gone: the page began
   on the middle of it. Anchored at the top instead, page zero lands on the
   figure's own pale lead-in and the ribbon barely registers at all. 10%
   cuts at row 328, a thirteenth of the way in, which keeps the taper and
   the first bend on the page.
   [decision 28 Sep, after rendering 0, 15, 30 and 50]

   THE WIDTH IS THE ZOOM. clamp(200px, 17vw, 300px) is the figure's share of
   the page, about a sixth, which is the proportion the integration page
   design uses: a slender ribbon with air around it and the strands reading
   as separate lines. Everything else follows from it: the height of the
   crop is whatever the section leaves, and the figure never repeats. At
   26vw the strands run together into one thick band.

   UP UNDER THE HEADER. The header is transparent at the top of the page,
   and a transparent header is only worth having when something is behind
   it. The section therefore starts at the top of the document rather than
   below the header, and pays the height back as padding so not a pixel of
   content moves.

   The header keeps z-index 20 and the container has 1, so the ribbon passes
   BEHIND both: it is seen through the header, never over the navigation.

   Measured, because the navigation sits on the figure rather than on plain
   ground. The strip under the header covers source rows 328 to 458 of the
   figure at this zoom, where it is still pale and
   the ground only reaches rgb(205, 225, 230). The links, the logotype and
   the CTA are all text-strong, which measures 9.24:1 there, against a limit
   of 4.5. Body colour would be 4.22:1 and there is none in the header.

   REDO THIS IF THE WIDTH CHANGES. The width is the zoom, the zoom decides
   the crop, and the crop decides which rows of the figure the navigation
   sits on. Below 1020 there is no ribbon at all.

   After the first 48px the surface and the hairline have faded in and the
   navigation is on solid white. */
.section--contact-page,
.section--ribbon {
  position: relative;
  overflow: hidden;
}
/* Less ground above and below than a section's full padding [Emilie 26 okt]:
   the page is one section, and at 112 it opened and closed on empty white. */
.section--contact-page {
  margin-top: calc(var(--header-height) * -1);
  padding-top: calc(min(var(--section-pad), var(--wp--preset--spacing--80)) + var(--header-height));
  padding-bottom: min(var(--section-pad), var(--wp--preset--spacing--80));
}
/* The contact page no longer draws its ribbon here; it hangs off the two
   columns instead, see "THE CONTACT PAGE'S RIBBON" below. */
.section--ribbon::before {
  content: "";
  position: absolute;
  z-index: 0;
  top: -80px;
  /* On the container's outer edge and up to 1vw past it; see the note
     above. Inset from the column it stands over the system grid. */
  right: calc(var(--outside-container) + clamp(-64px, -1vw, 0px));
  width: clamp(200px, 17vw, 300px);
  height: calc(100% + 160px);
  background: url("assets/media/flow.webp?v=2") center 10% / cover no-repeat;
  opacity: 0.55;
  transform: rotate(6deg);
  pointer-events: none;
}
/* THE SAME RIBBON IN THE HERO OF /artificial-intelligence/ [Emilie 16 okt],
   and in morkbla, not teal. The design system lets teal and cyan carry the
   ribbon only where it stands for data that moves; as mood in a hero it is
   morkbla on a light ground. flow-morkbla.webp is the same recipe as
   flow.webp, see assets/media/README.md.

   NOT UP UNDER THE HEADER, unlike the contact page. The header contrast
   above was measured on the teal file, and morkbla is darker on the rows
   the navigation would sit on. Starting below the header, the hero's own
   top edge cuts the ribbon instead and nothing has to be remeasured.

   TEXT STAYS OFF IT BY LAYOUT. Morkbla at this opacity reaches 1.95:1
   against body text, so the hero is one column: the lead is capped at 62ch
   and ends well left of the ribbon at every width it is drawn at. */
.section--ribbon::before {
  background-image: url("assets/media/flow-morkbla.webp?v=2");
  /* The contact page crops at 10% so the navigation sits on the figure's
     pale lead-in. Nothing sits on this one, and a hero is short: at 10% it
     showed only that lead-in, a grey smudge. 40% is the first bend and the
     strands splitting. */
  background-position: center 40%;
}
/* THE RIBBON ENDS ON THE NEXT LABEL'S RULE [Emilie 4 nov], where the next
   section opens on one (/karriar/). Cut at the hero's own edge it stopped
   in the empty padding between the two sections.

   THE HERO REACHES DOWN TO THE RULE AND GIVES THE SPACE BACK: the extra
   bottom padding and the negative margin cancel, so nothing below moves,
   and overflow hidden now cuts the ribbon on the rule's top edge. Not
   clip-path with overflow visible: the ribbon leans past the container and
   would give the page a sideways scroll, which clip-path does not prevent.

   The reach is the next section's top padding plus the label's line (body
   line height 1.6 at mikro) and its 16px padding. Redo it if the label
   changes. Only where the ribbon is drawn, because the overlapping hero
   sits over the label and would take its text selection. */
@media (min-width: 1021px) {
  .section--ribbon:has(+ .section > .container > .section-label:first-child) {
    --ribbon-reach: calc(var(--section-pad) + 1.6 * var(--wp--preset--font-size--mikro) + 16px);
    padding-bottom: calc(var(--section-pad) + var(--ribbon-reach));
    margin-bottom: calc(var(--ribbon-reach) * -1);
  }
}
/* The content sits above the ribbon, as on .section--contact. */
.section--contact-page > .container,
.section--ribbon > .container {
  position: relative;
  z-index: 1;
}

/* THE CONTACT PAGE'S RIBBON [Emilie 23 okt]: in the margin right of the
   content, from the top of the page down to the grey card, where it ends.
   It used to stand inside the column, behind the lead.

   HUNG OFF THE TWO COLUMNS, not the section. The card is the right column
   and starts where .contact-layout starts, so a pseudo element on the
   layout can end exactly there (bottom: 100%) however the heading and lead
   above it wrap. It reaches up past the top of the page and the section's
   overflow hidden cuts it there, under the transparent header.

   OUTSIDE THE CONTENT, NEVER OVER IT. left: 100% is the content's right
   edge, the card's and the lead's; the width is what lies between that edge
   and the window, capped at 160px. Nothing on the page is drawn in that
   margin, so no text sits on the ribbon and the contrast measurements below
   do not arise.

   ONLY WHERE THE MARGIN HOLDS IT. The margin is the gutter until the window
   passes the column, (V - 1700) / 2 + 48 after that. At 1820 it is 108px,
   enough for the figure to read as a ribbon and not a thread; below that it
   goes, rather than being squeezed or pushed over the words. */
.section--contact-page .contact-layout {
  position: relative;
}
.section--contact-page .contact-layout::before {
  content: none;
}
@media (min-width: 1820px) {
  .section--contact-page .contact-layout::before {
    content: "";
    position: absolute;
    z-index: -1;
    bottom: 100%;
    left: 100%;
    width: min(160px, calc((100vw - 100%) / 2));
    height: 200vh;
    /* The figure at the margin's width, its lower end on the card. */
    background: url("assets/media/flow.webp?v=2") center bottom / 100% auto no-repeat;
    opacity: 0.55;
    pointer-events: none;
  }
}

/* WHICH COLOURWAY, AND WHAT IT COSTS.

   The flow figure ships in five: cyan, teal, ljus, grafit and morkbla. Every
   colour in every palette was measured against the page ground at this
   opacity. Text-body over the strongest point of each:

     ljus     4.55:1   passes
     cyan     3.39:1   fails
     teal     2.52:1   fails
     morkbla  1.95:1   fails
     grafit   1.77:1   fails

   TEAL, which is the design file's own: its darkest colour is rgb(0,122,158)
   and the design's figure measures rgb(32,130,158). Cyan is a different
   thing and is not a candidate whatever it measured: its darkest colour is
   #00B2E2 exactly, the signal colour, and the signal colour is never carried
   by decoration. See the token block at the top of this file.

   Ljus is the only colourway a paragraph can sit on, and it is so pale that
   the ribbon reads as paper rather than as the design's figure. So teal,
   with body text kept off it by the two rules below. Swapping
   the file means redoing the measurement: it is per palette. */

/* Stacked, every text block runs the full width of the column and there is
   no way to keep it clear of the ribbon. So below the width where the two
   columns stack, the ribbon goes.

   THE FIGURE FOLLOWS FROM THE GRID, so redo it if the grid changes: the
   columns stack when the container is narrower than two 420px tracks plus
   the gap, spacing 80, which measures 81px: 921. The container is the
   viewport less two gutters, and the gutter is 4vw until it caps at 48,
   so V - 0.08V = 921 puts the stack just above 1001. 1020 is the figure
   from the 96px gap the
   grid had until 26 okt; kept, since it errs on the side of no ribbon. */
@media (max-width: 1020px) {
  .section--ribbon::before {
    display: none;
  }
}

.contact-layout {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 420px), 1fr));
  /* Both gaps are spacing presets. The design file has one clamp for
     both axes, from 56 to 112; neither end is on the scale, and the
     scale is what theme.json publishes to the editor. */
  /* One step down from 96 and 64 [Emilie 26 okt]: the page read as
     spread out. */
  column-gap: var(--wp--preset--spacing--80);
  row-gap: var(--wp--preset--spacing--70);
  align-items: start;
}
/* Core's flow layout puts 24px between siblings in a group. The grid
   already spaces its children, so the margin would be added to the gap.
   Same rule as .ownership, .columns, .buttons and .flow-row. */
.contact-layout > * {
  margin-block: 0;
  /* A grid column does not shrink below its content by default, and the
     form plugin's own markup is wide. Without this the column pushes the
     grid past the container instead of wrapping. */
  min-width: 0;
}

/* The ways to reach a human, under "Direktkontakt" in the right column's
   card [Emilie 23 okt]: a label over its value, a hairline over the first
   and under each. No icon beside the pair [Emilie 26 okt]. It is a list,
   and on the exemption list for the running measure. */
.contact-ways {
  display: grid;
  margin: 0;
  padding: 0;
  border-top: 1px solid var(--wp--preset--color--hairline);
  list-style: none;
}
.contact-ways__item {
  display: grid;
  margin: 0;
  padding-block: var(--wp--preset--spacing--50);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.contact-ways__label {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.4;
}
.contact-ways__value {
  /* An address is one unbroken word; at 320 it may need to break. */
  overflow-wrap: anywhere;
  color: var(--wp--preset--color--text-strong);
  font-size: var(--wp--preset--font-size--rubrik-1);
  line-height: 1.3;
  text-decoration: none;
}
.contact-ways__value:hover {
  text-decoration: underline;
  text-underline-offset: 3px;
}

/* The slot the plugin's form lands in. Deliberately almost nothing: a
   width and the space above it. Everything inside it belongs to Gravity
   Forms until README's question is answered. */
.form-slot {
  margin-top: var(--wp--preset--spacing--60);
}
/* The dark band's form is two fields and a button, so it is held to a
   measure instead of running the full width of the page. */
.form-slot--narrow {
  max-width: 40rem;
}
/* THE FULL FORM, SHORTENED, in a closing band [Emilie 23 okt]: the about
   page's demo band, as the design draws it. One centred column of 45rem
   holds the heading and the form: name and e-mail side by side, the
   message under them across the column, then the consent, the note and
   the button, centred.

   ONLY THE REQUIRED FIELDS. The optional company and phone are hidden,
   not removed: the form in Gravity Forms is unchanged and still has them
   wherever it is placed whole. Picked by what they are, a text field the
   form does not require, so a field added later follows the same rule.

   THE LABELS FLOAT IN THE FIELDS, as on every form (see "Floating
   labels"). They were hidden here, with the names in the placeholders,
   until the floating label replaced both [17 nov]. */
.section:has(.form-slot--compact) > .container > * {
  width: 100%;
  max-width: 45rem;
  margin-inline: auto;
}
/* The heading takes its own width rather than wrapping at the column, and
   stands centred over the form [Emilie 23 okt]. Narrower than its line,
   it wraps as any heading does, each line centred. */
.section:has(.form-slot--compact) > .container > :is(h1, h2) {
  width: auto;
  max-width: none;
  margin-inline: 0;
  text-align: center;
}
.form-slot--compact .gform_fields > :is(.gfield--type-text, .gfield--type-phone):not(.gfield_contains_required) {
  display: none;
}
/* At the weight of the plugin's size class (textarea.large sets a 288px
   minimum): the design's box is about half that. */
.form-slot--compact .gform_wrapper.gform-theme--orbital .gfield--type-textarea textarea.textarea {
  min-height: 0;
  height: 9.5rem;
}
/* The consent at the fields' text size. The plugin sizes it through its
   secondary label variable, resolved on the wrapper; set on the field, it
   wins there by inheritance. */
.form-slot--compact .gfield--type-consent {
  --gf-ctrl-label-font-size-secondary: 15px;
}
.form-slot--compact .gfield--type-html {
  color: var(--text-muted-on-dark);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.04em;
}
/* 12px IS THE FLOOR [Emilie 23 okt], as everywhere on the page. The
   plugin's note sits in a small, which took 83% of the 12 above to 10. */
.form-slot--compact .gfield--type-html small {
  font-size: inherit;
}
/* Less room under the button than a section's full padding: the band is
   the last thing before the footer [Emilie 23 okt]. */
.section:has(.form-slot--compact) {
  padding-bottom: min(var(--section-pad), var(--wp--preset--spacing--80));
}
.form-slot--compact .gform_footer {
  justify-content: center;
}
/* Name and e-mail on one row once there is room for two fields. */
@media (min-width: 720px) {
  .form-slot--compact .gform_fields {
    column-gap: var(--wp--preset--spacing--40);
  }
  .form-slot--compact .gform_fields > .gfield--type-text.gfield_contains_required {
    grid-column: 1 / span 6;
  }
  .form-slot--compact .gform_fields > .gfield--type-email {
    grid-column: 7 / span 6;
  }
}

/* THE SHORT FORM AT A FIELD'S WIDTH [Emilie 16 nov]: phone and e-mail side
   by side, the consent under them and the button under that, which is the
   plugin's own order. The front page's closing band, syncify/home-contact,
   with form 2.

   20rem A FIELD, NOT A SHARE OF THE ROW: stretched over the container each
   field ran to 468px at 1440, far longer than a phone number or an
   address. The plugin's grid halves what it is given, so it is given two
   fields and its own gap. At the plugin's own weight, which out-ranks a
   plain slot class. Below 720 the plugin stacks the fields as usual. */
.form-slot--inline .gform_wrapper.gform-theme--orbital .gform_fields {
  max-width: calc(40rem + var(--gf-form-gap-x));
}

/* WHAT STANDS THERE WHEN THE PLUGIN DOES NOT. Written by inc/forms.php, see
   that file for why it exists at all.

   A bordered box and not a bare line, because the empty slot is otherwise
   indistinguishable from a band that was meant to be short: the reader has
   to be able to tell that something is missing rather than that nothing was
   promised. The border and the radius are the card's, so it is recognisably
   a box this site draws.

   It inherits its ink, which is what makes it work on the dark band as well
   as on the white one without a second rule. */
.form-fallback {
  margin: 0;
  padding: var(--wp--preset--spacing--50);
  border: 1px solid currentColor;
  border-radius: var(--radius-card);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
  /* The border would shout at full strength; the words are the message. */
  border-color: color-mix(in srgb, currentColor 35%, transparent);
}
/* THE ADDRESS INHERITS THE BAND'S INK, like the box around it. Measured on
   the dark band at the foot of the contact page, the link took the page's
   ordinary link colour and came out at 1.2:1 against graphite: the words
   either side of it read and the address itself was a gap. Underlined,
   because inheriting the ink is what takes the colour difference away, and
   a link in a sentence has to be findable by something. */
.form-fallback a {
  color: inherit;
  text-decoration: underline;
  text-underline-offset: 3px;
}

.contact-aside > * {
  margin-block: 0;
}
/* THE RIGHT COLUMN IS A CARD [Emilie 23 okt]: "Direktkontakt" with the
   phone and the e-mail, then the systems, on the light surface and with
   no rules inside it. Opaque, so the ribbon behind the section stops at
   its edge. */
.contact-aside {
  padding: clamp(var(--wp--preset--spacing--50), 3vw, var(--wp--preset--spacing--60));
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--surface);
}
/* The space over the phone and over "Vanliga systemintegrationer" is the
   same [Emilie 23 okt], so the card reads as even steps. Stated here
   because the card's own reset above zeroes both margins. The same step
   under a lead, as on the partner category pages [Emilie 30 okt], where
   the list's rule stood flush against the last line of text. */
.contact-aside__text + .contact-ways,
.lead + .contact-ways,
.contact-ways + .contact-aside__heading,
.company-fold + .contact-aside__heading {
  margin-top: var(--wp--preset--spacing--60);
}
/* On the partner category pages a line between the lead and the list
   ("Frågor? Hör av er!") introduces the phone number, so it stands close
   to the list instead of a full step away [Emilie 9 nov]. */
.lead + p + .contact-ways {
  margin-top: var(--wp--preset--spacing--20);
}
/* The heading is a rung below the page's display sizes: the preset is
   rubrik-1 and the weight is the one theme.json gives every heading.
   The h2 element style is lighter than that, which is right under a
   display heading and wrong beside a column of fields. */
.contact-aside__heading,
.contact-main__heading {
  font-weight: 400;
}
/* The left column's heading opens it the way "Direktkontakt" opens the
   card on the right [Emilie 23 okt]. It was the section label "Kontakta
   oss" over both, with a graphite rule under it. */
.contact-main__heading {
  margin-block: 0;
}
/* The space between the page's hero, its heading and lead, and the two
   columns [Emilie 23 okt]. The label's margin used to hold them apart;
   with it gone the columns take the space themselves, and more of it, so
   the hero reads as the page's opening and not as the first section.
   From the scale's 48 up to its 64 [Emilie 26 okt]: at 144 the lead
   floated free of what it introduces. */
.section--contact-page .contact-layout {
  margin-top: clamp(var(--wp--preset--spacing--70), 6vw, var(--wp--preset--spacing--80));
}
/* The message box at about half the plugin's 288px minimum, as in the
   compact form below: at full height the form alone was 835px. */
.contact-main .gform_wrapper.gform-theme--orbital .gfield--type-textarea textarea.textarea {
  min-height: 0;
  height: 10rem;
}
/* The hero's lead runs as wide as the heading over it [Emilie 23 okt],
   not to the 62ch a lead keeps elsewhere. */
.section--contact-page .lead {
  max-width: none;
}
/* A line break for a wide window only [Emilie 23 okt]: set where a
   sentence should turn on desktop, gone where the column is narrow and
   the line wraps on its own. 1020, the width the contact columns stack
   at. */
.br-wide {
  display: none;
}
@media (min-width: 1020px) {
  .br-wide {
    display: inline;
  }
}
/* TEXT-STRONG, NOT BODY, because of the ribbon behind the section: body
   colour measured 2.52:1 over its strongest point, text-strong 5.52:1.
   The right column is now an opaque card and takes body colour below;
   the rule stays for any column the ribbon can still reach.

   Set by construction rather than by fitting the measure to today's
   sentence. The copy is not approved and the line will get longer or
   shorter, and a rule that depends on how far one sentence happens to reach
   is a rule that breaks silently when the sentence changes. */
.contact-aside__text,
.contact-main__text {
  max-width: 44ch;
  margin-top: var(--wp--preset--spacing--40);
  color: var(--wp--preset--color--text-strong);
  text-wrap: pretty;
}
.contact-aside__text {
  color: var(--wp--preset--color--text-body);
}
/* The same text on the left, under its heading and over the form
   [Emilie 23 okt]. The full width of its column, the width of the form
   under it, not the 44ch the right column's text keeps. */
.contact-main__text {
  max-width: none;
}

/* The grid of systems. Hairlines on two sides of the grid and two sides
   of every cell, so every rule is drawn exactly once whatever the column
   count is.

   FOUR COLUMNS, STATED, not auto-fill. The grid holds twelve marks and the
   design draws them four by three. Left to auto-fill the count follows the
   column width, and at five the last row is two cells and a hole; at 320 the
   cells are too narrow for the word inside them. Two counts, both of which
   divide twelve. */
.system-grid {
  display: grid;
  grid-template-columns: repeat(4, minmax(0, 1fr));
  margin-top: var(--wp--preset--spacing--60);
  border-top: 1px solid var(--wp--preset--color--hairline);
  border-left: 1px solid var(--wp--preset--color--hairline);
}
/* Four fixed columns leave about 76px a cell at 320, which is narrower
   than the word inside them, and the grid then pushes the page sideways.
   Two columns below 560 and one below 380. */
@media (max-width: 560px) {
  .system-grid {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }
}
@media (max-width: 380px) {
  .system-grid {
    grid-template-columns: minmax(0, 1fr);
  }
}

/* ------------------------------------------------------------------
   The logotypes the slots hold.

   Drawn by [syncify_logo] and [syncify_logos] out of the one list on the
   options page; see syncify_logo_by_slug() in inc/options.php. The slot
   shapes below set the box, these two set what stands in it.

   The height is the row's own, written as an inline style because it
   differs per mark and a class cannot carry a number. Width is left to
   the browser so the file's ratio decides it.

   .logo-missing IS FOR EDITORS AND NOBODY ELSE. A slug with nothing
   behind it, because it is misspelled or because its row is waiting for
   the control matrix, draws nothing at all for a visitor. For someone who
   can edit the site it names itself, so a logotype that quietly failed to
   appear is a logotype somebody notices. It is deliberately plain: it is
   scaffolding, not design, and it must not be mistaken for a chip.
   ------------------------------------------------------------------ */
.logo-mark {
  display: block;
  width: auto;
  max-width: 100%;
  object-fit: contain;
}
/* The dashed frame marks an empty slot. Once a mark sits in it the frame
   has nothing left to say. Transparent rather than none, so the slot keeps
   its size and the row does not shift by a pixel. */
.system-list__slot:has(.logo-mark),
.connector-card__slot:has(.logo-mark),
.system-cell__slot:has(.logo-mark) {
  border-color: transparent;
}
.logo-missing {
  padding: 2px var(--wp--preset--spacing--20);
  border: 1px dashed var(--wp--preset--color--graphic);
  border-radius: 4px;
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  white-space: nowrap;
}

/* SCAFFOLDING, the same as the partner band's slots and for the same
   reason: guardrail 7 rules out a system or customer mark until the list
   is checked against the control matrix. The cells hold the grid's rhythm
   and height until the marks arrive. */
.system-grid__slot {
  /* The track can only shrink if the slot can. A bare fraction keeps an
     auto minimum, and the slot then set the track to the width of the word
     inside it, which pushed the page sideways at 320. */
  min-width: 0;
  overflow-wrap: anywhere;
  display: flex;
  align-items: center;
  justify-content: center;
  min-height: 96px;
  margin: 0;
  padding: var(--wp--preset--spacing--40);
  border-right: 1px solid var(--wp--preset--color--hairline);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
  /* Opaque, so the flow ribbon passes BEHIND the grid rather than through
     it. The design states the same white on every cell, and it is the
     reason the marks stay readable where the ribbon crosses them. */
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.08em;
  /* start, NOT center. v.1 sets everything left. On one line the flex
     centring above still places the label, so this shows when the label
     wraps: the second line lines up under the first instead of hugging the
     middle. It wraps at 360 today.

     The flex centring itself is left alone. It places the MARK that goes
     in this slot, not the text, and moving a logotype to the left edge of
     its cell is a design decision rather than a text alignment one. */
  text-align: start;
  text-transform: uppercase;
  /* The label is one word and the cell can now be narrower than it. It
     breaks rather than pushing the cell wider; a logotype, which is what
     goes here, has no such problem. */
  overflow-wrap: break-word;
}

/* Narrow: two columns. The cells are 120px wide at the design width, and
   below roughly 600 the column cannot hold four of them and the word inside
   starts to break. */
@media (max-width: 600px) {
  .system-grid {
    grid-template-columns: repeat(2, 1fr);
  }
}

/* ------------------------------------------------------------------
   Security page.

   Seven bands, and almost all of them open the same way: the section
   label, then a heading and a short paragraph side by side, then the
   material. That opening is .band-head, built once here rather than six
   times in the patterns.

   The material below it is one of three shapes, and they are the whole of
   this block: grouped checklists (.check-groups), rows split into a narrow
   left and a wide right (.split-rows), and a paragraph set off by a rule
   (.statement). The hero's row of figures (.facts) went 16 nov [Emilie].

   NO NEW COLOUR AND NO NEW TYPE SIZE. The surfaces are graphite,
   graphite deep and surface from theme.json's palette; the muted ink on
   dark is the footer's token. Where the design's own value is not a step
   on a scale the theme publishes, the nearest step is used and the
   difference is listed in ATT-GORA.md rather than invented here.
   ------------------------------------------------------------------ */

/* The opening of a band: heading left, a short paragraph right, aligned
   at the bottom so the paragraph sits on the heading's last line rather
   than floating beside its middle. */
.band-head {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 420px), 1fr));
  column-gap: var(--wp--preset--spacing--90);
  row-gap: var(--wp--preset--spacing--50);
  align-items: end;
}
/* A BAND HEAD THAT OPENS A PAGE NEEDS ITS COLUMNS WIDER [Emilie 6 okt].
   Measured at 1440: the container holds 1329, so the 96px gap leaves two
   columns of 616.5. Two call to action buttons want 629 together, and
   wrapped to a second row on two pages at a cost of 60px of band height
   each. The heading ran to three and four lines in the same 616.

   The gap steps down to spacing 70 rather than being given a number of
   its own. A column is then 637 and the buttons fit with 8 to spare,
   which is not much; the next step up does not fit at all. Note that this
   preset is 54px and not the 48 theme.json asks for, because WordPress's
   own spacing scale shadows that slug; it is under the cap either way,
   and the fault is written up in ATT-GORA.md.

   The illustration beside the words gets WIDER here, not narrower, so it
   also gets shorter. That is why the gap gives rather than the column
   split: on one of these pages the panel is the taller column.

   The condition picks these bands out, not a class on each. It reads as
   "a band head whose first column carries buttons", which is five bands
   on the site, counted rather than assumed: the four page openings this
   was written for, and the integrationer page's graphite band, which has
   the same two column shape and the same pair of buttons. Everywhere
   else the design's 96 stands. */
.band-head:has(> :first-child > .buttons) {
  column-gap: var(--wp--preset--spacing--70);
}
/* THE CLASS IS DOUBLED ON PURPOSE. A band head's gaps own the spacing
   inside it, so a column must not bring its own block margin. One class
   was not enough: .record-rows, .system-cells and .form-slot each set a
   margin-top of their own at the same specificity and later in the file,
   so they won. It did not show while the columns were aligned at the
   bottom; once they aligned at the top the right hand column sat 56, 64
   and 54 pixels below the left on three pages. Doubling the class costs
   nothing and needs no list to keep in step. */
.band-head.band-head > * {
  margin-block: 0;
  min-width: 0;
}

/* THE SECTION LABEL IS A ROW, NOT A COLUMN. Eight of these bands kept
   their label inside the left column, so its rule stopped at the column
   edge: 617px of a 1329px measure at 1440, with the right column's own
   rule starting again further along. Every other label on the site draws
   across the whole container.

   The label is lifted out of the column in the patterns and sits here as
   the grid's first child. This is what makes it span.

   THE MARGIN IS THE ROW GAP SUBTRACTED. .band-head > * zeroes the block
   margins because the grid's gaps own the spacing, and the row gap is
   24px while a section label stands clamp(32px, 4vw, 56px) above what
   follows it everywhere else. Taking the gap off the margin leaves the
   same distance under this label as under all the others: 56px at 1440,
   32 at the floor. */
.band-head > .section-label {
  grid-column: 1 / -1;
  margin-bottom: calc(clamp(32px, 4vw, 56px) - var(--wp--preset--spacing--50));
}
/* AND A LABEL THAT SPANS KEEPS A THIRD TRACK ALIVE. auto-fit only folds
   away a track nothing sits in, and the label's 1 / -1 sits in all of
   them. Once the container holds three 420px tracks and two 96px gaps,
   1452 and up, a window of roughly 1550 to 1560, the grid makes three, the
   label spans them and the two columns fill two: a third of the band stood
   empty beside the direction table on the process page.

   The track floor is raised to half the row, so two always fit and three
   never do. The pixel off the half is headroom: two halves and the gap sum
   to exactly the row, and a browser that rounds the floor up by a fraction
   would fit one. Under 938 the 420 floor is the larger and the band stacks
   exactly where it did, so nothing changes on a tablet or a phone. The
   prose inside keeps its own measure (.lead, .statement--fine), so its
   lines grow only up to that, 62ch at most; the panels are what widen. */
.band-head:has(> .section-label) {
  grid-template-columns: repeat(auto-fit, minmax(max(min(100%, 420px), calc((100% - var(--wp--preset--spacing--90)) / 2 - 1px)), 1fr));
}
/* THE BOTTOM ALIGNMENT ONLY MAKES SENSE AGAINST A PARAGRAPH, and seven
   of these bands put something else in the second column: a panel, the
   record list, the system cells. Those are taller than the words beside
   them, so bottom alignment dropped the label, the heading and the lead
   to the foot of the section with empty ground above them. Measured at
   1440 the drop was 204px on order till betalning, 181 on integrationer,
   179 and 121 on ekonomisk-avstamning.

   Said as a condition rather than as a class on each one, because the
   condition is what decides it: a band head is bottom aligned when its
   second column is .band-head__text and top aligned otherwise. A new
   band gets it right without anyone remembering a modifier.

   .band-head--top stays. It names the same thing for the heads that
   DO carry a paragraph and still want the top, and it is written after
   the base rule so it keeps winning. */
.band-head:not(:has(> .band-head__text)) {
  align-items: start;
}

/* A BAND HEAD WITH BUTTONS CENTRES ITS TWO COLUMNS [Emilie 6 okt], so
   the shorter column sits in the middle of the taller one rather than
   hanging from the top with the whole difference as empty ground below.
   align-items on the row, not align-self on one column, because which
   column is the taller varies.

   Written for the four page openings with a panel. Those are heroes, and
   since 5 nov a hero starts its heading at the same height on every page
   instead, see THE HEADING STARTS AT THE SAME HEIGHT. What this still
   centres is the same shape further down a page: the integrationer page's
   graphite band.

   IT SITS BEFORE .band-head--top ON PURPOSE. A head that names the top
   explicitly still gets it; this only changes the ones that fell into
   top alignment by not carrying a paragraph. */
.band-head:has(> :first-child > .buttons) {
  align-items: center;
}

.band-head--top {
  align-items: start;
}

/* THE PARAGRAPH'S CAPITALS ON THE HEADING'S [Emilie 16 nov]. Top aligned,
   both boxes start level, but the 1.12 heading carries more room above its
   capitals than the 1.6 paragraph, so the paragraph stood 3px higher at
   1440. The margin is the difference between the two cap offsets.

   A line's capitals start (line-height - 1.4em) / 2 + 1.05em - 1cap below
   its box: 1.4em and 1.05em are Poppins' ascent plus descent and its
   ascent. For the heading that is 0.213 of its size, which is
   .display--sub's clamp repeated here; change that clamp and this goes
   out by a pixel or two. The paragraph's half is written in its own units.

   Side by side only, from the 1020 the rule for a head whose second
   column is a control uses. This head stacks until about 1033 (two 420
   tracks and the 96 gap), so between the two the stacked paragraph gets
   under a pixel of extra room, which is not worth a breakpoint of its
   own. Used by the GDPR band on /sparbarhet/ alone. */
@media (min-width: 1020px) {
  .band-head.band-head--cap-line > .band-head__text {
    margin-top: calc(0.213 * clamp(1.875rem, 2.5vw + 0.75rem, 3.25rem) - ((1lh - 1.4em) / 2 + 1.05em - 1cap));
  }
}

/* A HEAD WITH ITS TEXT UNDER THE HEADING [Emilie 13 nov]. One column, and
   the heading drops .display--sub's 20ch cap so it runs the container
   instead of breaking at 472px. A modifier because nothing in the markup
   tells this head from a side by side one; the choice is the designer's.
   The class is doubled to win over .band-head:has(> .section-label). Used
   by the incident band on /sparbarhet/. */
.band-head.band-head--stacked {
  grid-template-columns: minmax(0, 1fr);
}
.band-head--stacked > .display--sub {
  max-width: none;
}

/* A HEADING BESIDE A FORM TAKES ITS COLUMN [Emilie 13 nov]. .display--sub's
   20ch cap is 472px at 1440 against a 927px column, so "Saknas ert system
   i listan?" broke in two with half the column empty. The column is the
   measure here; text-wrap: balance still evens the lines when it has to
   break. Only the integrationer graphite band has this shape today. */
.band-head:has(> .form-slot) > :first-child > .display--sub {
  max-width: none;
}

/* A BAND HEAD WHOSE SECOND COLUMN IS A CONTROL, not a paragraph and not
   a panel. The integrations band on the partner page did this until
   23 okt, and it wants neither of the two alignments above: a 48px button
   held at the top of its column against a heading that runs to two lines
   sits level with the heading first line and reads as floating.

   Centred against the heading, and at the far end of its own column.
   Written as the condition rather than as a class, the same as the rule
   above it, so a second band of this shape needs no modifier.

   THE END ALIGNMENT ONLY APPLIES WHILE THERE ARE TWO COLUMNS. The grid is
   auto-fit over minmax(min(100%, 420px), 1fr) with a 96px gap, so it
   stacks when the container drops under 936, which is a viewport of about
   1017. Stacked, a button ranged right under a heading ranged left reads
   as a mistake, so it keeps the heading edge there. 1020 is the figure the
   contact page already rounds this to. */
.band-head:has(> .buttons) {
  align-items: center;
}
@media (min-width: 1020px) {
  /* THE BUTTON TAKES ITS OWN WIDTH, NOT HALF THE BAND. Two equal columns
     are right when the second one holds words; here it holds a 190px
     button, and the other half of the band was being spent on nothing
     while the heading broke over two lines. auto gives the button what it
     needs and the heading the rest: 1058 of 1344 at full width, against
     the 834 the heading wants on one line. */
  .band-head:has(> .buttons) {
    grid-template-columns: minmax(0, 1fr) auto;
  }
  /* And the heading takes that column. .display--sub caps at 20ch, which is
     653px at this size, so the measure and not the column would have been
     what broke it. Only here: section headings keep their measure
     everywhere else. */
  .band-head:has(> .buttons) > :is(h1, h2, h3) {
    max-width: none;
  }
  .band-head > .buttons {
    justify-content: flex-end;
  }

  /* A HEAD WHOSE WORDS ARE A HEADING AND A LEAD keeps two equal halves,
     with the button centred in the right one [Emilie 19 okt]. The button
     takes its own width above for a lone heading that wants the whole
     line; a heading with a lead under it is already set to a measure,
     and the button pushed to the far edge read as detached from it.

     The condition is the words column being a wrapper, not a heading:
     two bands today, the partner page's closing band and the contact
     band on every integration page. */
  .band-head:has(> div + .buttons) {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }
  .band-head > div + .buttons {
    justify-content: center;
  }
}
.band-head__text {
  max-width: 52ch;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}
.section--dark .band-head__text {
  color: var(--text-muted-on-dark);
}
/* A short claim alone beside the heading, in place of a paragraph
   [Emilie 28 okt]. Ingress size in the heading's ink, 500 so it reads as a
   statement and not as running text. Centred on the heading: it is two
   lines against two, and neither the bottom alignment a paragraph gets
   nor the top a panel gets puts it level with both. */
.band-head__claim {
  max-width: 52ch;
  font-size: var(--wp--preset--font-size--ingress);
  font-weight: 500;
  line-height: 1.6;
  color: var(--wp--preset--color--text-strong);
}
.band-head:has(> .band-head__claim) {
  align-items: center;
}
/* A lead under a band head runs the band's full width [Emilie 28 okt]. It
   sits under both columns, and the 62ch measure would stop it short of
   the right hand one. */
.band-head + .lead {
  max-width: none;
}

/* Grouped checklists. The tick is a CSS mask from the theme's own Heroicons
   path, so it takes the text's colour and needs no markup an editor
   could break. Icons sit beside text, never alone, never in the signal
   colour. */
.check-groups {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 280px), 1fr));
  gap: var(--wp--preset--spacing--80) var(--wp--preset--spacing--70);
  margin-top: clamp(56px, 6vw, 88px);
}
.check-groups > * {
  margin-block: 0;
}
.check-group {
  padding-top: var(--wp--preset--spacing--50);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.section--dark .check-group {
  border-top-color: var(--hairline-color-dark);
}
.check-group__label {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.section--dark .check-group__label {
  color: var(--text-muted-on-dark);
}
.check-list {
  margin: var(--wp--preset--spacing--50) 0 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: var(--wp--preset--spacing--40);
  /* Rubrik 2, not body size [Emilie 15 nov]: at 15px the four points read
     as small print under a display heading. */
  font-size: var(--wp--preset--font-size--rubrik-2);
  line-height: 1.6;
  color: var(--wp--preset--color--text-body);
}
.section--dark .check-list {
  color: var(--wp--preset--color--text-on-dark);
}
.check-list li {
  display: flex;
  align-items: flex-start;
  gap: var(--wp--preset--spacing--30);
}
.check-list li::before {
  content: "";
  flex: none;
  /* In em so the mark follows the text; the margin centres it on the
     first line, (1.6em - 1em) / 2. */
  width: 1em;
  height: 1em;
  margin-top: 0.3em;
  background-color: var(--wp--preset--color--text-strong);
  -webkit-mask: var(--icon-check) center / contain no-repeat;
  mask: var(--icon-check) center / contain no-repeat;
}
.section--dark .check-list li::before {
  background-color: var(--wp--preset--color--text-on-dark);
}

/* Rows divided by hairlines: a narrow left column that names the thing
   and a wide right one that explains it. Used for the incident steps on
   /sparbarhet/, the rows on /kundanpassad-integration/ and the quote form
   pattern. */
.split-rows {
  margin: clamp(48px, 5vw, 72px) 0 0;
  padding: 0;
  list-style: none;
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.split-row {
  display: flex;
  flex-wrap: wrap;
  gap: var(--wp--preset--spacing--30) var(--wp--preset--spacing--90);
  padding-block: var(--wp--preset--spacing--60);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.split-row > * {
  margin-block: 0;
}
.split-row__title {
  flex: 1 1 260px;
  margin: 0;
  /* rubrik-1, NOT rubrik-2: at 18px the heading would be smaller than the
     19px body text beside it. See .trust__title. */
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.35;
}
.split-row__body {
  flex: 2 1 420px;
  max-width: 68ch;
}
.split-row__text {
  margin: 0;
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}
.split-row__title + .split-row__text {
  margin-top: var(--wp--preset--spacing--30);
}
/* A paragraph set off by a rule above it. Two uses: the statement that
   closes the ground section, in graphite because it is the page's claim,
   and the caveat at the foot of the page, smaller and in body colour
   because it is a qualification and not a claim. */
.statement {
  margin: clamp(56px, 6vw, 88px) 0 0;
  padding-top: var(--wp--preset--spacing--50);
  border-top: 1px solid var(--wp--preset--color--graphite);
  max-width: 60ch;
  font-size: var(--wp--preset--font-size--ingress);
  line-height: 1.5;
  text-wrap: pretty;
}
.statement strong {
  font-weight: 500;
}
/* The fine print under a band. NO RULE ABOVE IT, 2 okt, on request: it
   inherited .statement's top border, and because the paragraph is capped
   at 52ch the rule stopped with the text rather than spanning anything.
   A hairline that ends in the middle of a band reads as a leftover. */
.statement--fine {
  margin-top: clamp(48px, 5vw, 72px);
  padding-top: 0;
  border-top: 0;
  max-width: 52ch;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
}
/* On a dark band the same line is body coloured on graphite, 2.75:1.
   It is fine print and still text, so it takes the muted on dark ink.
   The border colour is for .statement; .statement--fine has no border. */
.section--dark .statement,
.section--dark .statement--fine {
  color: var(--text-muted-on-dark);
}
.section--dark .statement {
  border-top-color: var(--hairline-color-dark);
}
/* NO SECOND RULE UNDER A LABEL [Emilie 14 nov]. A band whose label already
   draws a hairline would show two lines a heading apart, which reads as a
   table frame. Where the container has a section label, the statement
   keeps its space and loses its own rule. Today that is the security page
   ("Vem äger vad"); the AI page's statement has no label and keeps it. */
.container:has(> .section-label) > .statement:not(.statement--fine) {
  padding-top: 0;
  border-top: 0;
}

/* The closing band used to open on a rule of its own, drawn on the
   container. It opens on its section label now, "Kontakta oss" over the
   label's hairline [Emilie 16 nov], so that rule is gone: two would sit a
   label apart. */
/* ONE PADDING AT THE BOUNDARY, NOT TWO, the pair .section--flows and
   .section--contact use. Two light bands meeting put two full section
   paddings between the last list and the rule: 205px at 1280 [measured
   14 nov], where the front page's same boundary is 135. The talk band
   opens on its label's rule, so the space above it is the step that can
   give.

   The integration page's onward links are the same boundary: a light band
   opening on a rule, its section label's, after another light band. 237px
   from the last line to the links at 1280 [measured 14 nov]. */
.section:has(+ :is(.section--talk, .section--integration-onward)) {
  padding-bottom: var(--wp--preset--spacing--80);
}
:is(.section--talk, .section--integration-onward) {
  padding-top: var(--wp--preset--spacing--70);
}
.note-under {
  margin: var(--wp--preset--spacing--50) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--wp--preset--color--text-body);
}

/* ------------------------------------------------------------------
   About page.

   Four bands: an intro with a picture across the page, two panels that
   mirror each other around two landscape photographs, and the dark
   demo band.

   MOST OF IT IS ALREADY HERE. The dark band's two columns are
   .contact-layout, the ways to reach a human are .contact-ways, the form
   drops into .form-slot, and the section label and its rule are the
   theme's. What is new below is the mirrored panel, the picture frames
   and the logotype grid.

   NO PICTURE SHIPS WITH A TEMPLATE. Every frame here draws a tint in
   surface colour and nothing else, the same rule .media-card follows and
   for the same reason: a placeholder image that travels with the code is
   an image that reaches production.
   ------------------------------------------------------------------ */

/* The intro heading. Two lines, the second heavier, so the claim and the
   sentence under it read as one block rather than a heading and a
   subheading. */
/* Same as .hero-heading: this one sets its own lines and does not want the
   17ch that comes with .display--page. */
.about-heading {
  max-width: none;
  margin: 0;
  line-height: 1.08;
  text-wrap: balance;
}
/* The column beside the intro heading: paragraphs and a button, stacked
   and left aligned, sitting on the heading's baseline. */
.band-head__col {
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: var(--wp--preset--spacing--50);
  margin-block: 0;
  min-width: 0;
}
.band-head__col > * {
  margin-block: 0;
}

/* THE ABOUT PAGE'S OPENING, IN THREE [Emilie 26 okt]: the heading, the
   animated symbol, and the words with the button. The symbol takes its
   own width and the two text columns share the rest. Stacked, one column:
   heading, symbol, words. The columns were centred on each other until
   5 nov; as the page's hero they now stand at the top, see THE HEADING
   STARTS AT THE SAME HEIGHT. */
.band-head.band-head--symbol {
  grid-template-columns: minmax(0, 1fr);
}
@media (min-width: 1020px) {
  .band-head.band-head--symbol {
    grid-template-columns: minmax(0, 1.1fr) auto minmax(0, 1fr);
    column-gap: var(--wp--preset--spacing--80);
  }
}
/* --s is the symbol's size. The file is 1.225 times that, the extra being
   room for the halves to fly in, and the negative margin gives the room
   back so the layout sees only the symbol. See inc/media.php. */
.about-symbol {
  --s: clamp(120px, 13vw, 220px);
  display: block;
  width: calc(var(--s) * 1.225);
  max-width: none;
  height: auto;
  margin: calc(var(--s) * -0.1125);
}

/* A picture that has not been chosen yet. The ratio comes from the
   element so one class serves every shape; both photographs on the
   about page are landscape [Emilie 17 nov].

   A tint, never a picture. When a real image is put inside, it fills the
   frame and the tint is behind it. */
.media-frame {
  /* WIDTH FIRST, THEN THE RATIO. Without an explicit width an empty box
     with aspect-ratio and a min-height derives its WIDTH from the ratio:
     the wide frame came out 640px inside a 342px column at a 390 window
     and put a sideways scroll on the page. With the width stated, the
     ratio only ever decides the height, and min-height raises it where
     the frame would otherwise be a slot. */
  width: 100%;
  aspect-ratio: var(--ratio, 16 / 7);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--surface);
  overflow: hidden;
}
.media-frame img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
}
/* The two mirrored panels. Vision puts the picture first and the words
   second; mission does the reverse, in source order, so the reading
   order and the visual order agree at every width and no direction has
   to be reversed with CSS. */
.split-pair {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 380px), 1fr));
  /* spacing 60 between rows (36 measured), 96 between columns. The row
     gap only exists once
     the two have stacked, which is where the picture and the words want
     to sit close [Emilie 22 okt]. */
  gap: var(--wp--preset--spacing--60) var(--wp--preset--spacing--90);
  align-items: center;
}
.split-pair > * {
  margin-block: 0;
  min-width: 0;
}
.split-pair__media {
  max-width: 420px;
}
/* STACKED, THE PICTURE COMES FIRST [Emilie 22 okt], whichever side it
   stands on beside the words. Side by side nothing changes.

   A container query on the pair itself, because the stacking is the
   grid's auto-fit and not a media query: two columns need 2 x 380 + the
   96px gap = 856px of content width, and below that there is one. The
   query asks the same question of the same box, so the two cannot
   disagree at any window width. */
.split-pair {
  container: split-pair / inline-size;
}
@container split-pair (max-width: 855.98px) {
  .split-pair__media {
    order: -1;
  }
  /* The words close up under the picture [Emilie 22 okt]: the row gap
     and nothing more, so the panel's own room above the words goes.
     Inside the pair, because .quote-panel's own rule comes later. */
  .split-pair .quote-panel {
    padding-top: 0;
  }
}

/* The words half of a panel: a heading, the quotation and a paragraph.
   NO RULE ABOVE IT [Emilie 22 okt]; the space it stood in stays, so
   nothing on the page moves. */
.quote-panel {
  padding-top: var(--wp--preset--spacing--60);
}
.quote-panel > * {
  margin-block: 0;
}
.quote-panel__quote {
  max-width: 22ch;
  margin: var(--wp--preset--spacing--50) 0 0;
  font-size: var(--wp--preset--font-size--display-2);
  font-weight: 300;
  line-height: 1.25;
  letter-spacing: -0.01em;
  text-wrap: balance;
}
.quote-panel__text {
  max-width: 52ch;
  margin: var(--wp--preset--spacing--50) 0 0;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}
.quote-panel .buttons {
  margin-top: var(--wp--preset--spacing--60);
}

/* THE ABOUT PAGE'S PAIRS [Emilie 26 okt]: "Varför vi finns", and vision
   and mission together on the surface. Each statement opens under a
   section label with its rule, the words and the picture start on the
   same line, and the picture fills its column instead of the 420px a
   portrait keeps beside a quotation. */
.split-pair--about {
  align-items: start;
}
.split-pair--about .split-pair__media {
  max-width: none;
}
.split-pair--about .quote-panel {
  max-width: 35rem;
  padding-top: 0;
}
.split-pair--about .section-label {
  margin-bottom: var(--wp--preset--spacing--60);
}
/* The second statement in the column, a step clear of the first. */
.split-pair--about .quote-panel__text + .section-label {
  margin-top: var(--wp--preset--spacing--90);
}
.split-pair--about .buttons {
  margin-top: var(--wp--preset--spacing--80);
}
/* IN BLACK AND WHITE [Emilie 28 okt], both photographs on the page. A
   filter and not a converted file, so a picture chosen in wp-admin under
   Bilder is grey too and the files keep their colour. */
.split-pair--about .media-frame img {
  filter: grayscale(1);
}
.media-frame--landscape {
  --ratio: 4 / 3;
}
/* On the surface the frame takes the page's ground, or it would vanish
   into the section behind it. */
.section--surface .media-frame {
  background: var(--wp--preset--color--ground);
}

/* THE HISTORY [Emilie 11 nov]: the years on one line, a node on the line
   for each, and a hairline down from each node that divides the columns.

   THE FILLED NODE IS THE LAST ONE, by :last-child and not by a class, so
   it stays on the newest year whatever an editor writes into the six.
   Graphite, not cyan: the node is structure, and cyan is reserved for data
   that moves or deviates.

   THE LINE AND THE NODES ARE PSEUDO ELEMENTS, so the pattern holds core
   blocks and words only and contentOnly leaves nothing to break.

   Six across from 1200. The longest word in a title, Processförbättring,
   is 184px at 20px and 166 at 18; at 1440 a column holds 198 after its
   padding, at 1200 about 160. The title steps down with the window to fit,
   and below 1200 it would not, so the line stands up instead: it runs down
   the left edge through every node and stops at the last. Hyphenation is
   not the fix: Chrome on Windows has no Swedish dictionary, and the word
   broke before its last letter with no hyphen. */
.history {
  --history-node: 13px;
  --history-year-size: clamp(2.25rem, 1.5vw + 1.5rem, 3rem);
  margin-top: var(--stack-lg);
}
.history__item {
  position: relative;
  margin-block: 0;
  padding: 0 0 var(--wp--preset--spacing--70) calc(var(--history-node) + var(--wp--preset--spacing--40));
  border-left: 1px solid var(--wp--preset--color--hairline);
  margin-left: calc(var(--history-node) / 2);
}
.history__item:last-child {
  padding-bottom: 0;
  border-left-color: transparent;
}
.history__item::before {
  content: "";
  position: absolute;
  /* Stacked, the node stands level with the middle of the year's line.
     Moved on the node and not on the year, because the flow layout zeroes
     the first child's top margin at two classes of specificity. */
  top: calc(var(--history-year-size) * 0.6 - var(--history-node) / 2);
  left: calc(var(--history-node) / -2 - 0.5px);
  width: var(--history-node);
  height: var(--history-node);
  box-sizing: border-box;
  border: 1px solid var(--wp--preset--color--graphite);
  border-radius: 50%;
  background: var(--wp--preset--color--ground);
}
.history__item:last-child::before {
  background: var(--wp--preset--color--text-strong);
  border-color: var(--wp--preset--color--text-strong);
}
.history__item > * {
  margin-block: 0;
}
.history__year {
  font-size: var(--history-year-size);
  font-weight: 300;
  line-height: 1.2;
  letter-spacing: -0.02em;
  color: var(--wp--preset--color--text-strong);
  font-variant-numeric: tabular-nums;
}
.history__title {
  margin-top: var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--ingress);
  font-weight: 400;
  line-height: 1.3;
}
.history__text {
  max-width: 52ch;
  margin-top: var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.8;
  color: var(--wp--preset--color--text-body);
}
@media (min-width: 1200px) {
  .history {
    position: relative;
    display: grid;
    grid-template-columns: repeat(6, minmax(0, 1fr));
    padding-top: calc(var(--history-node) / 2);
  }
  /* The one line across, through the middle of every node. */
  .history::before {
    content: "";
    position: absolute;
    top: calc(var(--history-node) / 2);
    left: 0;
    right: 0;
    height: 1px;
    background: var(--wp--preset--color--hairline);
  }
  .history__item,
  .history__item:last-child {
    margin-left: 0;
    padding: calc(var(--history-node) / 2 + var(--wp--preset--spacing--60)) 0 0 var(--wp--preset--spacing--50);
    border-left-color: var(--wp--preset--color--hairline);
  }
  .history__item:first-child {
    padding-left: 0;
    border-left-color: transparent;
  }
  .history__item::before {
    top: calc(var(--history-node) / -2);
  }
  .history__item:first-child::before {
    left: 0;
  }
  .history__title {
    font-size: clamp(1rem, 1.25vw, 1.25rem);
  }
  /* The text keeps off the next column's rule. The title does not: at
     1200 Processförbättring needs all 158px the column has. */
  .history__text {
    padding-right: var(--wp--preset--spacing--30);
  }
}

/* ------------------------------------------------------------------
   The service provider's details, lagen om elektronisk handel 8 §.

   A description list: every line is a label and a value, which is what
   a dl is for and what lets a screen reader say which is which. Quiet
   by design. The law asks that these be easy to find, not that they be
   the loudest thing on the page, and on the contact page they sit under
   the form [Emilie 23 okt], after the two ways to reach a human.

   The labels keep their own column so the values line up, and the
   column is sized to the longest of them, Organisationsnummer. Below
   the wrap the label stands over its value instead.
   ------------------------------------------------------------------ */
/* The disclosure the list sits in: the third row of the contact card,
   under the phone and the e-mail and drawn the same way [Emilie 23 okt].
   The building, the title at the values' size, the chevron at the far end;
   the hairline under it closes the rows. Opened, the list stands under the
   title, in from the edge by the mark and its gap so it lines up with the
   words. */
.company-fold {
  margin: 0;
  border-bottom: 1px solid var(--wp--preset--color--hairline);
  font-size: var(--wp--preset--font-size--brod-liten);
}
.company-fold__summary {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  align-items: center;
  column-gap: var(--wp--preset--spacing--40);
  /* 44px at least, so the row is a target and not a line of text that
     happens to be clickable. WCAG 2.5.8. */
  min-height: 44px;
  padding-block: var(--wp--preset--spacing--50);
  color: var(--wp--preset--color--text-strong);
  font-size: var(--wp--preset--font-size--rubrik-1);
  line-height: 1.3;
  cursor: pointer;
  /* The browser's own triangle is replaced by the mark below, and it has
     to be turned off in two ways: Safari reads the webkit pseudo element
     and the rest read list-style. */
  list-style: none;
}
.company-fold__summary::-webkit-details-marker {
  display: none;
}
/* A chevron that turns up when the fold is open. A COPY of chevron-down in
   inc/icons.php, which is the source. Beside a word that says what it
   opens, as the design system's icons always are. */
.company-fold__mark {
  width: 18px;
  height: 18px;
  background-color: currentColor;
  -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m19.5 8.25-7.5 7.5-7.5-7.5'/%3E%3C/svg%3E") center / contain no-repeat;
  mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m19.5 8.25-7.5 7.5-7.5-7.5'/%3E%3C/svg%3E") center / contain no-repeat;
  transition: transform var(--dur-hover) var(--ease);
}
.company-fold[open] .company-fold__mark {
  transform: rotate(180deg);
}
.company-fold .company-card {
  padding-left: calc(18px + var(--wp--preset--spacing--40));
}
.section--dark .company-fold {
  border-top-color: var(--hairline-color-dark);
}
.section--dark .company-fold__summary {
  color: var(--wp--preset--color--text-on-dark);
}

.company-card {
  margin: 0 0 var(--wp--preset--spacing--50);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
}
.company-card__row {
  display: grid;
  grid-template-columns: minmax(0, 15rem) minmax(0, 1fr);
  gap: var(--wp--preset--spacing--20) var(--wp--preset--spacing--40);
}
.company-card__row + .company-card__row {
  margin-top: var(--wp--preset--spacing--30);
}
.company-card__label {
  margin: 0;
  color: var(--wp--preset--color--text-body);
}
.company-card__value {
  margin: 0;
  color: var(--wp--preset--color--text-strong);
  /* The number is a figure and reads as one. */
  font-variant-numeric: tabular-nums;
}
.company-card__value a {
  color: inherit;
}
.section--dark .company-card__label {
  color: var(--text-muted-on-dark);
}
.section--dark .company-card__value {
  color: var(--wp--preset--color--text-on-dark);
}
/* One column where 15rem of label plus a value stops fitting. */
@media (max-width: 600px) {
  .company-card__row {
    grid-template-columns: 1fr;
  }
}

/* ON A DARK BAND THE LINK COLOUR HAS TO BE SAID. theme.json gives every
   link text-strong, which is the right answer on the page ground and
   unreadable on graphite deep: measured at 1.55:1 before this rule, and
   15.73:1 after it. The section colour does not reach them on its own,
   because a link sets its own colour and inherits nothing. */
.section--dark .contact-ways__value {
  color: var(--wp--preset--color--text-on-dark);
}
/* The label's body ink measured 2.18:1 on graphite; the muted ink on dark
   measures 4.77:1. */
.section--dark .contact-ways__label {
  color: var(--text-muted-on-dark);
}
.section--dark .contact-ways__value:hover {
  color: var(--wp--preset--color--surface);
}

/* The customer logotype grid. One hairline between cells, drawn as a gap
   over a coloured backing rather than as a border on each cell, so the
   lines are single everywhere and the outer edge is one line too.

   EMPTY BY GUARDRAIL 7. No customer mark goes anywhere until the list is
   checked against the control matrix for partner and customer names. The
   cells hold the grid's rhythm until then, exactly as the partner band's
   slots and the contact page's system grid do.

   FOUR COLUMNS, STATED, not auto-fill, for the same reason as the system
   grid: the grid holds eight marks, and auto-fill settled on five, which
   left a row of three and a hole. Two counts, both of which divide eight. */
.logo-grid {
  display: grid;
  /* minmax(0, 1fr), NOT 1fr [8 okt]. A bare 1fr is minmax(auto, 1fr), so a
     column cannot go under its own content, and the label in these cells is
     one unbreakable word. On om-oss the grid stands in the narrower of two
     columns and overflowed the page by 14px at 1020, measured; the page
     scrolled sideways. */
  grid-template-columns: repeat(4, minmax(0, 1fr));
  gap: 1px;
  margin-top: var(--wp--preset--spacing--60);
  background: var(--hairline-color-dark);
  border: 1px solid var(--hairline-color-dark);
}
.logo-grid__slot {
  display: flex;
  align-items: center;
  justify-content: center;
  aspect-ratio: 3 / 2;
  margin: 0;
  padding: var(--wp--preset--spacing--30);
  background: var(--wp--preset--color--graphite-deep);
  color: var(--text-muted-on-dark);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.08em;
  /* start, NOT center. v.1 sets everything left. On one line the flex
     centring above still places the label, so this shows when the label
     wraps: the second line lines up under the first instead of hugging the
     middle. It wraps at 360 today.

     The flex centring itself is left alone. It places the MARK that goes
     in this slot, not the text, and moving a logotype to the left edge of
     its cell is a design decision rather than a text alignment one. On the
     list for the review with Mattias. */
  text-align: start;
  text-transform: uppercase;
}

/* No rule and no padding above the customer logotype heading [2 okt, on
   request], so both columns of .contact-layout start on the same edge. */
.demo-aside {
  padding-top: 0;
}
.demo-aside > * {
  margin-block: 0;
}
/* The heading over the logotype grid, a rung below the band's own h2. */
.demo-aside__title {
  margin: 0;
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.2;
  letter-spacing: -0.01em;
}
.demo-aside__text {
  max-width: 46ch;
  margin: var(--wp--preset--spacing--40) 0 0;
  line-height: 1.7;
  color: var(--text-muted-on-dark);
  text-wrap: pretty;
}

/* Narrow: two columns, so the word inside a cell still fits. */
@media (max-width: 600px) {
  .logo-grid {
    grid-template-columns: repeat(2, 1fr);
  }
}

/* ------------------------------------------------------------------
   Process page.

   Six bands. Two of them carry a white card on a coloured ground: the
   hero's transaction log and the direction table. That card is .panel,
   built once and used twice.

   The rest is one shape repeated: a label, a title and a short text,
   eight times over. That is .feature-col, and .feature-grid is the row
   it sits in.

   THE STATUS COLOURS ARE NEW, and they are the design system's own, with
   its measured ratios kept beside them. They live here and not in
   theme.json's palette for the same reason the signal colour does: a
   palette entry becomes selectable as a background and a text colour in
   the block editor, and a status is a meaning the product assigns, not a
   colour an editor picks.
   ------------------------------------------------------------------ */
:root {
  /* Semantic status, muted and dark rather than pastel, so each carries
     4.5:1 against white and against its own tint. The ratios are the
     design system's, quoted rather than recomputed. */
  --status-ok: #14735A;              /* 5.8:1 on white */
  --status-warning: #7E5C1C;         /* 6.1:1 on white */
  --status-ok-surface: #E8F1EF;
  --status-warning-surface: #F2EFE8;
}

/* ------------------------------------------------------------------
   Panels, and the four colours that decide which surface one is on.

   A white card on a coloured ground: a head with a title and a note, a
   body, and an optional foot in surface colour.

   A PANEL IS LIGHT ON EVERY SURFACE [Emilie 14 okt]. Every log picture is
   a white card, on a dark band as much as on a light one, and the
   transaction log follows the same values. .panel--dark is still in the
   integrationer page's markup and in its post_content, and has no rule:
   it is inert, not wrong.

   Stated as properties, so the rows inside and the components that can
   sit outside a panel read one set of names with their own fallbacks.

   THE DARK BAND STILL REACHES IN. A .section--dark descendant rule
   matches inside a panel, so any rule of that shape that styles something
   a panel can hold has to say :not(.panel *). The status chip is the one
   that did it before, at 2.28:1.
   ------------------------------------------------------------------ */
.panel {
  --panel-bg: var(--wp--preset--color--ground);
  --panel-ink: var(--wp--preset--color--text-strong);
  --panel-rule: var(--wp--preset--color--hairline);
  --panel-chrome: var(--wp--preset--color--surface);
  --panel-quiet: var(--wp--preset--color--text-body);

  border: 1px solid var(--panel-rule);
  border-radius: var(--radius-card);
  background: var(--panel-bg);
  color: var(--panel-ink);
  overflow: hidden;
  /* The panels are timestamps and ids. A column of figures that does not
     line up reads as a different kind of thing than a log. */
  font-variant-numeric: tabular-nums;
}
.panel > * {
  margin-block: 0;
}
.panel__head {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  justify-content: space-between;
  gap: var(--wp--preset--spacing--30);
  padding: var(--wp--preset--spacing--30) var(--wp--preset--spacing--40);
  border-bottom: 1px solid var(--panel-rule);
  background: var(--panel-chrome);
}
.panel__title {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
}
.panel__meta {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  color: var(--panel-quiet);
}
.panel__body {
  padding: var(--wp--preset--spacing--40);
}
.panel__foot {
  margin: 0;
  padding: var(--wp--preset--spacing--30) var(--wp--preset--spacing--40);
  border-top: 1px solid var(--panel-rule);
  background: var(--panel-chrome);
  font-size: var(--wp--preset--font-size--mikro);
  line-height: 1.55;
  color: var(--panel-quiet);
  text-wrap: pretty;
}

/* The direction table: which record flows which way. A list, not a
   table element, because there is one column of content and two of
   annotation, and it has to reflow to one column on a phone. */
.dir-rows {
  margin: 0;
  padding: 0;
  list-style: none;
}
.dir-row {
  display: grid;
  grid-template-columns: minmax(0, 1.3fr) minmax(96px, 1fr) minmax(96px, auto);
  gap: var(--wp--preset--spacing--40);
  align-items: center;
  padding-block: var(--wp--preset--spacing--40);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.dir-row > * {
  margin-block: 0;
}
.dir-row--head {
  align-items: end;
  padding-block: var(--wp--preset--spacing--30);
  border-top: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.dir-row__ends {
  display: flex;
  justify-content: space-between;
}
.dir-row__post {
  margin: 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  font-weight: 500;
}
/* 8 AND NOT 2. Two pixels under a 500 weight title made the note read as
   the title's second line. On the scale rather than off it. */
.dir-row__note {
  margin: var(--wp--preset--spacing--20) 0 0;
  font-size: var(--wp--preset--font-size--mikro);
  line-height: 1.5;
  color: var(--wp--preset--color--text-body);
}
/* The rule between the two systems, with a mark at whichever end leads. */
.dir-row__line {
  position: relative;
  height: 9px;
}
.dir-row__line::before {
  content: "";
  position: absolute;
  inset-inline: 0;
  top: 4px;
  height: 1px;
  background: var(--wp--preset--color--hairline);
}
.dir-row__line::after {
  content: "";
  position: absolute;
  top: 1px;
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: var(--wp--preset--color--graphite);
}
.dir-row__line--to-erp::after { right: 0; }
.dir-row__line--to-crm::after { left: 0; }
.dir-row__line--both::before { background: var(--wp--preset--color--graphite); }
/* Both directions: one dot in the middle of the line. A dot at each end
   reads as two separate destinations rather than as one exchange. */
.dir-row__line--both::after {
  left: 50%;
  transform: translateX(-50%);
}
.dir-row__dir {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  text-align: right;
}
/* One column on a phone: the annotations go under the record rather than
   beside it, because 96px of rule beside 13px of text is neither. */
@media (max-width: 560px) {
  .dir-row {
    grid-template-columns: 1fr;
    gap: var(--wp--preset--spacing--20);
  }
  .dir-row--head {
    display: none;
  }
  .dir-row__dir {
    text-align: left;
  }
}

/* The page's repeated shape: a small label, a title, a paragraph. Eight
   of them, so it is a component and not eight blocks of markup. */
.feature-grid {
  display: grid;
  /* Named because the ownership pair below measures its rule against it.
     One value, read by the gap and by that rule, so the line cannot end
     up somewhere the columns do not. */
  --feature-gap: clamp(32px, 4vw, 64px);
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 280px), 1fr));
  gap: var(--wp--preset--spacing--70) var(--feature-gap);
  margin-top: clamp(40px, 5vw, 72px);
}
.feature-grid > * {
  margin-block: 0;
}
.feature-col {
  padding-top: var(--wp--preset--spacing--60);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
/* The three steps on integrationsplattform: a numbered node per step, and
   one hairline that runs from each node to the next.

   A STAIRCASE, NO MOVING NODE [Emilie 22 okt]. Each step sits one drop
   lower than the one before, and the line bends down between them. The
   line is still; nothing travels along it.

   The node and the line are pseudo elements, so the copy and the markup
   stay as they are. The modifier is in the pattern and in post_content.
   Also the scenarios under "Problemet" on ekonomisk-avstamning [Emilie
   22 okt], which were cards; their Konsekvens comes along under the text.
   And the three steps on erp-byte [Emilie 29 okt], which were cards too.

   The drop is a fixed length, not a clamp, because the bend is a mask
   drawn at that exact size: stretched, the stroke would thicken where the
   curve is steep. Below 900 the row is one column and the line runs
   straight down from node to node. 900 because the plain grid already
   held three columns there, at about 250px each. */
.feature-grid--steps {
  --step-node: 40px;
  --step-drop: 44px;
  counter-reset: step;
  grid-template-columns: minmax(0, 1fr);
}
.feature-grid--steps .feature-col {
  position: relative;
  counter-increment: step;
  padding-top: 0;
  padding-left: calc(var(--step-node) + var(--wp--preset--spacing--40));
  border-top: 0;
}
.feature-grid--steps .feature-col::before {
  content: counter(step);
  position: absolute;
  top: 0;
  left: 0;
  z-index: 1;
  display: grid;
  place-items: center;
  width: var(--step-node);
  height: var(--step-node);
  box-sizing: border-box;
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: 50%;
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
  font-size: 13px;
  font-variant-numeric: tabular-nums;
}
.feature-grid--steps .feature-col:not(:last-child)::after {
  content: "";
  position: absolute;
  top: var(--step-node);
  bottom: calc(-1 * var(--wp--preset--spacing--70));
  left: calc(var(--step-node) / 2);
  width: 1px;
  background: var(--wp--preset--color--hairline);
}
@media (min-width: 900px) {
  .feature-grid--steps {
    grid-template-columns: repeat(3, minmax(0, 1fr));
    padding-bottom: calc(2 * var(--step-drop));
  }
  .feature-grid--steps .feature-col {
    padding-top: calc(var(--step-node) + var(--wp--preset--spacing--50));
    padding-left: 0;
  }
  .feature-grid--steps .feature-col:nth-child(2) {
    transform: translateY(var(--step-drop));
  }
  .feature-grid--steps .feature-col:nth-child(3) {
    transform: translateY(calc(2 * var(--step-drop)));
  }
  /* From the right edge of a node to the left edge of the next: straight,
     then one bend down by the drop, then straight into the node. The last
     step's line runs on to the edge of its column. */
  .feature-grid--steps .feature-col::after,
  .feature-grid--steps .feature-col:not(:last-child)::after {
    content: "";
    position: absolute;
    top: calc(var(--step-node) / 2);
    bottom: auto;
    left: var(--step-node);
    width: calc(100% - var(--step-node));
    height: 1px;
    background: var(--wp--preset--color--hairline);
  }
  .feature-grid--steps .feature-col:not(:last-child)::after {
    width: calc(100% + var(--feature-gap) - var(--step-node));
    height: calc(var(--step-drop) + 1px);
    -webkit-mask:
      url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='96' height='45' viewBox='0 0 96 45'%3E%3Cpath d='M0 .5C40 .5 40 44.5 80 44.5H96' fill='none' stroke='%23000'/%3E%3C/svg%3E") right top / 96px 100% no-repeat,
      linear-gradient(#000 0 0) left top / calc(100% - 96px) 1px no-repeat;
    mask:
      url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='96' height='45' viewBox='0 0 96 45'%3E%3Cpath d='M0 .5C40 .5 40 44.5 80 44.5H96' fill='none' stroke='%23000'/%3E%3C/svg%3E") right top / 96px 100% no-repeat,
      linear-gradient(#000 0 0) left top / calc(100% - 96px) 1px no-repeat;
  }
  /* THE LABEL STANDS ON THE LINE, beside its node [Emilie 29 okt]. It is
     lifted out of the column onto the node's row, and its ground backing
     covers the line under it, so the line reads as starting after the word.
     The ground is the node's own assumption: both sit on a light band.
     Under 900 the label already stands beside the node, so nothing moves. */
  .feature-grid--steps .feature-col__label {
    position: absolute;
    top: 0;
    left: var(--step-node);
    z-index: 1;
    display: flex;
    align-items: center;
    height: var(--step-node);
    padding-inline: var(--wp--preset--spacing--40);
    background: var(--wp--preset--color--ground);
  }
}
.feature-col > * {
  margin-block: 0;
}
.feature-col__label {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.feature-col__title {
  margin: var(--wp--preset--spacing--30) 0 0;
  /* rubrik-1, NOT rubrik-2: at 18px the heading would be smaller than the
     19px body text beside it. See .trust__title. */
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.35;
}
.feature-col__text {
  max-width: 42ch;
  margin: var(--wp--preset--spacing--30) 0 0;
  font-size: 15px;
  line-height: 1.6;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}
/* On a dark band the same two lines are body coloured on graphite, which
   measures 2.19:1. The column was written for a light band and the rules
   that lift text on a dark one are keyed to .section--dark, which never
   reached it. Same fault as the lead, the section label and the fine print
   before it. */
.section--dark .feature-col__text {
  color: var(--text-muted-on-dark);
}
.section--dark .feature-col__label {
  color: var(--wp--preset--color--surface);
}
/* And the rule over each column, which was the light band's hairline:
   #D9DFE3 on graphite, the brightest line in a band where every other
   divider is the dark hairline. Found when "Så gör Syncify" on
   ekonomisk-avstamning moved to this grid [Emilie 26 okt]. */
.section--dark .feature-col {
  border-top-color: var(--hairline-color-dark);
}

/* The card grid does the same, and for the same reason. Here the columns
   were already bottom aligned, by .card-grid__text's flex: 1, so the rules
   lined up; what varied was the distance ABOVE them. Measured at 1440 the
   last line of the text stood 3, 3, 3, 38, 63, 63 and 98px over the rule
   across the three pages, because the slack went wherever the text was
   short. Three pixels is a sentence touching a line.

   Subgrid gives the text one row height, so the gap is the consequence's
   own margin everywhere. That margin has to be said again here:
   .card-grid__item > * zeroes the block margins and comes later in the
   file, which is why it was 0 on these three pages and 32 on the process
   page, and why raising it changed nothing visible here. */
@supports (grid-template-rows: subgrid) {
  .card-grid__inner:has(.consequence) {
    grid-template-rows: auto auto 1fr auto;
  }
  .card-grid__inner:has(.consequence) > .card-grid__item {
    display: grid;
    grid-row: span 4;
    grid-template-rows: subgrid;
    /* A subgrid inherits the parent's gaps, and the scenario grid now has
       one between its cards. Without this the 24px would also open between
       the label, the heading, the text and the consequence INSIDE each
       card, where the spacing is each element's own margin. */
    row-gap: 0;
  }
  .card-grid__inner:has(.consequence) .consequence {
    margin-top: var(--wp--preset--spacing--60);
  }
}

/* THE RULES ABOVE Konsekvens LINE UP ACROSS THE COLUMNS. Without this the
   rule sits wherever the text above it happens to end: at 1440 the middle
   title runs to two lines and the other two to three, which put its rule
   38px above theirs.

   Subgrid, so the label, the title, the text and the consequence each get
   a row that all the columns share. The text row takes the slack, which is
   what lets the row below it start at one height.

   row-gap: 0 because a subgrid inherits the parent's gaps, and the 48px
   there is the distance between ROWS OF COLUMNS. Inside a column the
   spacing is each element's own margin, which is where it already was.

   Behind @supports: without subgrid the columns do what they did before,
   which is readable and merely unaligned.

   NOT THE STEPS. .feature-grid--steps stands its columns a drop apart on
   purpose, so there is no level for the rules to keep; this, the card
   box, its padding and its gap below all leave it alone. */
@supports (grid-template-rows: subgrid) {
  .feature-grid:has(.consequence):not(.feature-grid--steps) {
    grid-template-rows: auto auto 1fr auto;
  }
  .feature-grid:has(.consequence):not(.feature-grid--steps) > .feature-col {
    display: grid;
    grid-row: span 4;
    grid-template-rows: subgrid;
    row-gap: 0;
  }
}

/* The consequence under the first three columns: a second rule and the
   sentence that says what the situation costs. */
.consequence {
  /* 32 and not 24: at 24 the last line of the longest text stood 26px
     over the rule, which read as cramped. The rules stay level with each
     other because the subgrid gives the text row the same height in all
     three. */
  margin-top: var(--wp--preset--spacing--60);
  padding-top: var(--wp--preset--spacing--40);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
/* No rule over Konsekvens in the steps [Emilie 22 okt]. The space above
   still sets it apart; the scenario cards elsewhere keep their rule. */
.feature-grid--steps .consequence {
  padding-top: 0;
  border-top: 0;
}
/* Nor where it is a band head's second column, beside the heading rather
   than under a text [Emilie 29 okt]. The section label's rule already
   runs above both columns. Today that is erp-byte only. */
.band-head > .consequence {
  padding-top: 0;
  border-top: 0;
}
.consequence > * {
  margin-block: 0;
}
.consequence__label {
  margin: 0;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.consequence__text {
  max-width: 42ch;
  margin: var(--wp--preset--spacing--20) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
}

/* The two system lists.

   EMPTY BY GUARDRAIL 7, names as well as marks. The design names six
   products and loads their logotypes, one of them from syncify.se, which
   guardrail 1 rules out on its own. Until the control matrix for partner
   and customer names clears, the rows hold the rhythm and say nothing.
   Same treatment as the partner band and the contact page's grid. */
.system-list > * {
  margin-block: 0;
}
.system-list__label {
  margin: 0 0 var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.system-list__rows {
  margin: 0;
  padding: 0;
  list-style: none;
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.system-list__row {
  display: flex;
  align-items: center;
  gap: var(--wp--preset--spacing--50);
  padding-block: var(--wp--preset--spacing--40);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.system-list__slot {
  display: flex;
  align-items: center;
  justify-content: center;
  flex: none;
  width: 128px;
  height: 40px;
  border: 1px dashed var(--wp--preset--color--hairline);
  border-radius: var(--radius-button);
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.08em;
  text-transform: uppercase;
}
.system-list__name {
  margin: 0;
  font-size: 15px;
  font-weight: 500;
  color: var(--wp--preset--color--text-strong);
}

/* The flow figure behind the transaction log.

   A SECOND FILE, NOT THE SAME ONE. assets/media/flow.webp has white baked
   in where its alpha was, so on a dark band it paints a white pillar.
   assets/media/README.md prescribes the answer: a second file, matted on
   the surface it will sit on, rather than swapping the first.

   AND A DIFFERENT COLOURWAY, measured rather than assumed. Against
   graphite the brightest part of each figure reaches:

     ljus     3.61:1   reads
     cyan     2.54:1   reads, but decoration never carries the signal colour
     teal     1.65:1   nearly the ground itself
     morkbla  1.12:1   invisible

   Which is the opposite of the contact page, where ljus was too pale on
   white and teal was right. The figure has to be lighter than what it
   sits on, so the choice flips with the ground.

   It hangs on the panel's own bed rather than on the section, so it
   follows the card at every width instead of being positioned twice.

   THE BED IS AS TALL AS THE BAND, not as tall as the card. Sized to the
   card the figure had room for its middle only, and what showed above and
   below the card were two flat slabs with cut ends. Stretched to the row,
   the crop is long enough that the figure tapers, which is the only way it
   reads as a ribbon passing behind something. */
.panel-bed {
  position: relative;
  align-self: stretch;
  display: flex;
  flex-direction: column;
  justify-content: center;
}
.panel-bed::before {
  content: "";
  position: absolute;
  z-index: 0;
  /* Centred on the card's right edge, not on the card. Half the figure
     then runs behind the card and half outside it, so what shows above and
     below the card stands at the right edge rather than in the middle. */
  left: 100%;
  /* PAST THE BAND AT BOTH ENDS, so the figure is cut by the section and
     not by its own box. Ended inside the band it showed two flat slabs
     with sawn ends above and below the card; the exposed strip is too
     short for the taper, which runs over the whole length of the figure.
     Overflow hidden on the section does the cutting. */
  top: -80%;
  width: clamp(200px, 17vw, 300px);
  height: 260%;
  background: url("assets/media/flow-dark.webp?v=2") center 22% / cover no-repeat;
  opacity: 0.55;
  transform: translateX(-50%) rotate(6deg);
  pointer-events: none;
}
/* The card sits on top of it, opaque, so the figure is seen around the
   card and never through it.

   BOTH CARDS. The process page's bed holds .portal-figure now and the connectors
   page's still holds .panel. Named rather than written as a child
   selector, because the figure showing through the card is not subtle and
   the next card dropped in here should fail loudly rather than quietly. */
.panel-bed > .panel,
.panel-bed > .txlog,
.panel-bed > .portal-figure {
  position: relative;
  z-index: 1;
}

/* Below the width where the band's two columns stack, the figure goes.
   Stacked, the bed is a row of its own under the words, and a box that
   reaches 80 per cent above it lands behind the heading and the lead:
   checked at 900 and at 390, where it overlapped both. The figure lightens
   graphite towards rgb(126, 139, 152) at its brightest, which is within a
   few points of the muted ink the lead is set in, so it would take that
   text to roughly 1.2:1.

   Same figure as the contact page, and the same arithmetic: the columns
   stack when the container is narrower than two 420px tracks plus the 96px
   gap, which puts it just above 1017. */
@media (max-width: 1020px) {
  .panel-bed::before {
    display: none;
  }
}

/* The hero clips it: rotated and overhanging, the figure would otherwise
   reach past the band it belongs to. */
.section--process-hero {
  position: relative;
  overflow: hidden;
}
/* ------------------------------------------------------------------
   Integrationer page.

   Five bands. Most of it is already in the theme: the check list from the
   security page, the panel and its transaction rows from the process
   page, the closing band with its ribbon from the front page.

   What is new is the specification rows inside the panel, the connector
   cards and the ruled list.

   No status colours for graphite: panels are light on every surface, so
   no status sits on graphite. The design system has an inverse pair if
   one ever does.
   ------------------------------------------------------------------ */

/* The opening band of the integrationer page. Dark, with the flow figure
   entering at its top right.

   NOT A FULL SCREEN [Emilie 6 okt]. Only the front page opens on a band
   sized to the window; this one is as tall as what is in it, a heading
   and a lead. At 100svh three fifths of it would be empty.

   NOT THE OVER-HERO HEADER, for the same reason: its swap is a scroll
   range written against 100svh, so over a shorter band the navigation
   would stay white past the point the dark ended. The page takes
   over-ground with white ink over the pulled up band, see "Over a dark
   opening band" [Emilie 6 nov]. */
.section--tall {
  position: relative;
  overflow: hidden;
}
/* The flow figure, entering at the top right and cut by the band.

   A THIRD MATTE. flow.webp is matted on white and flow-dark.webp on
   graphite; this band is graphite deep, so it takes flow-deep.webp.
   Measured against that ground, the figure's brightest point reaches
   3.64:1 in ljus, 2.60:1 in cyan and 1.74:1 in teal, so ljus again. */
.section--tall::before {
  content: "";
  position: absolute;
  z-index: 0;
  top: -30%;
  right: max(var(--gutter), calc((100% - var(--container-max)) / 2 - 40px));
  width: clamp(200px, 20vw, 360px);
  height: 160%;
  background: url("assets/media/flow-deep.webp?v=2") center 18% / cover no-repeat;
  /* 0.42 AND NOT THE DESIGN'S 0.5, measured. The heading and the
     navigation both cross the figure, and both are white. At 0.5 the
     figure's brightest point takes white to 4.20:1, which clears the 3:1
     a 60px heading is held to but not the 4.5:1 a navigation link is. At
     0.42 white reaches 5.14:1 and the figure still stands 3.06:1 off the
     ground, so it is still a figure. */
  opacity: 0.42;
  transform: rotate(-14deg);
  pointer-events: none;
}
/* Below the width where the band's text runs full width, the figure goes.
   The lead is set in the muted ink, which reaches 1.96:1 over the figure
   at this opacity and never clears 4.5:1 at any opacity that leaves a
   figure to look at: 3.14:1 at 0.25, where it is almost gone. So the
   answer is not a fainter figure, it is text that does not cross it.
   Checked at 900 and 390, where the lead did. */
@media (max-width: 1020px) {
  .section--tall::before {
    display: none;
  }
}
.section--tall > .container {
  position: relative;
  z-index: 1;
  /* The band is a flex column, and margin-inline: auto on a flex item turns
     OFF the stretch and shrinks it to its content. It did not show while
     the heading was a full width grid; the moment the heading took a 17ch
     measure, the container shrank to 836 of 1329 and centred itself, and
     the whole band went with it. Same line, same reason, as
     .section--platform-hero > .container. */
  width: 100%;
}

/* Two sentences, one under the other: the halves are lines of one
   heading. No max-width of its own; .display--page beside it sets the
   measure. */
.hero-heading {
  margin: 0;
  line-height: 1.12;
}
.hero-heading__part {
  display: block;
  min-width: 0;
  text-wrap: balance;
}
/* The connector cards.

   EMPTY BY GUARDRAIL 7, and the count is out by guardrail 4. The design
   fills each card with a vendor logotype and a product name, and puts a
   per category tally on its filter tabs. Neither can ship until the
   control matrix for partner and customer names clears, and the tally is
   the connector count that CLAUDE.md keeps off the site because the two
   figures in circulation disagree and neither is verified.

   The cards hold the grid's rhythm until then, the same as the partner
   band's slots and the contact page's system grid. */
/* FOUR COLUMNS, STATED, for the third time in this file and the same
   reason each time: the grid held eight cards, auto-fill settled on five,
   and the last row was three cards and two holes. Two counts, both of
   which divide eight and the twelve it holds now. */
.connector-grid {
  display: grid;
  grid-template-columns: repeat(4, 1fr);
  gap: var(--wp--preset--spacing--40);
  margin-top: clamp(40px, 5vw, 64px);
}
/* Logotype on the left, name over category beside it. Stacked, the card
   left its right half empty. A grid and not a wrapper, so the pattern's
   markup and the stored pages stay as they are. The name's column never
   goes below its longest word; the slot gives way instead, or the name
   ran out of the card at 1024. */
.connector-card {
  display: grid;
  grid-template-columns: minmax(0, 120px) minmax(min-content, 1fr);
  align-items: center;
  justify-items: start;
  column-gap: var(--wp--preset--spacing--40);
  row-gap: var(--wp--preset--spacing--20);
  padding: var(--wp--preset--spacing--50);
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--ground);
}
.connector-card > * {
  margin-block: 0;
}
.connector-card > .chip {
  align-self: start;
}
.connector-card__slot {
  grid-row: span 2;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 120px;
  /* The slot is a fixed width and the card has 24px of padding either side,
     so the card cannot be narrower than 168px. Without this the grid track
     was forced past the window at 320 and the page scrolled sideways. */
  max-width: 100%;
  height: 52px;
  border: 1px dashed var(--wp--preset--color--hairline);
  border-radius: var(--radius-button);
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.08em;
  text-transform: uppercase;
}
.connector-card__name {
  align-self: end;
  margin: 0;
  font-size: 15px;
  font-weight: 500;
  line-height: 1.35;
}
/* A hub with no type field gets no chip, and the name sat in the top half
   of the card above an empty row. Last child means there is no chip. */
.connector-card__name:last-child {
  grid-row: span 2;
  align-self: center;
}
/* The cards drawn by [syncify_integration_hub_cards] are not links
   [Mattias 16 nov], see inc/integrations.php. The post's image fills the
   slot's height; the slot's own width and contain keep a wide mark inside it. */
.connector-card__slot > .logo-mark {
  height: 100%;
}

/* The note under the button in the custom connector band.

   UNDER THE BUTTON, at 1440 and at 390, and with margin 0 it would sit ON
   it. A control and the sentence that qualifies it need to be two things.
   One step on the spacing scale, not a number. */
.button-note {
  max-width: 34ch;
  margin: var(--wp--preset--spacing--50) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.5;
  color: var(--wp--preset--color--text-body);
}
.section--dark .button-note {
  color: var(--text-muted-on-dark);
}

/* Two columns from 1200 down, not 900: with the name beside the logotype
   a quarter of the row is too narrow for both below that. */
@media (max-width: 1200px) {
  .connector-grid {
    grid-template-columns: repeat(2, 1fr);
  }
}
/* One column on a phone. Two tracks of 132px cannot hold a 120px slot and
   48px of padding, measured at 320. */
@media (max-width: 600px) {
  .connector-grid {
    grid-template-columns: 1fr;
  }
}

/* ------------------------------------------------------------------
   ERP migration page.

   The hero is the theme's own .section--hero: the film, the mood layer
   and the scrim, reused rather than rebuilt. The page marks its main
   region --film-hero, which gives the sections after the hero their sheet
   and takes the front page's full height, sticky position and pull up off
   the hero; see .site-main--film-hero > .section--hero.

   New here: the bordered grid the scenarios and the steps sit in, and the
   small diagram in the hero panel.
   ------------------------------------------------------------------ */
:root {
  /* The deviation mark, darkened. The signal colour itself reaches only
     2.5:1 on white, under the 3:1 that WCAG 1.4.11 asks of a graphical
     object that carries meaning. This is the design system's own darkened
     value at 3.6:1. The signal colour stays what it is; this is what the
     mark is DRAWN in when it has to be seen. */
  --status-deviation: #0093BE;
  /* The same meaning as text, darker still because text is held to 4.5:1
     and a graphical object only to 3:1. On its own tint: 6.2:1. */
  --status-deviation-ink: #006A87;
  --status-deviation-surface: #E5F4FA;
}

/* The hero headline on this page and the reconciliation page. It sits
   below the front page hero's 150px scale: the design caps it at 84 and
   .display tops out at 68, which is the nearest the theme has. The bold
   half is the design's own emphasis, the same device .hero__heading
   carries on the front page.

   No measure. These h1s sit in a hero column rather than in the
   container, so the column is what holds them. */
.hero-headline {
  max-width: none;
}
.hero-headline b,
.hero-headline strong {
  font-weight: 500;
}

/* A grid whose cells are divided by hairlines rather than by gaps. The
   left rule is on every cell and the container is pulled one pixel left,
   so the outer edge has none and the inner ones are single. Rows divide
   with a top rule on each cell, which works however many land per row. */
.card-grid {
  overflow: hidden;
  margin-top: var(--stack-lg);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.card-grid__inner {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 300px), 1fr));
  margin-left: -1px;
}

/* ------------------------------------------------------------------
   THE EDITOR'S FLOW MARGIN ON A GRID CELL.

   A group block lays its children out as flow and gives every child
   but the first a 24px margin-block-start. When the theme turns that
   group into a grid, the margin comes along: cell one sits where the
   row starts and every other cell sits 24px lower, while all of them
   still stretch to the row's bottom edge.

   It is invisible until a cell draws a rule. On the step grids it did:
   the top hairline over cell one ran 24px above the one over cells two
   and three, measured on ekonomisk-avstamning at 1440 as 1313 against
   1337, and the same on erp-byte and order till betalning. On the
   connector grid it added 24px to a gap that was already declared.

   ADD A SELECTOR HERE WHEN A GROUP BLOCK BECOMES A GRID. The rule
   cannot be written once for every grid, because plenty of them want
   their children's margins; this is for the ones whose children are
   cells in a row.
   ------------------------------------------------------------------ */
.card-grid__inner > *,
.connector-grid > * {
  margin-block: 0;
}
.card-grid__item {
  display: flex;
  flex-direction: column;
  border-top: 1px solid var(--wp--preset--color--hairline);
  border-left: 1px solid var(--wp--preset--color--hairline);
}
/* The room inside a cell, written once. Two grids draw cards out of this
   and the step grid draws cells, and all three want the same breathing
   space; see the card rule below. */
.card-grid__item,
.feature-grid:has(.consequence):not(.feature-grid--steps) > .feature-col {
  padding: clamp(28px, 3vw, 44px) clamp(20px, 2.5vw, 40px);
}
.card-grid__item > * {
  margin-block: 0;
}

/* THE SCENARIOS ARE CARDS [Emilie 6 okt]. Each one is its own box: a
   border all the way round, the card radius the panels use, and a gap
   between them instead of a shared hairline.

   NOT THE STEP GRID. A numbered sequence in separate boxes stops being a
   sequence, so the steps keep the shared hairlines. The condition says
   that rather than a new class, so the markup is untouched and the three
   pages that carry this grid need no second pass through the database.

   NO FILL. A card on this page is a border and nothing else: the design
   is explicit that rhythm is carried by hairlines and not by alternating
   white and grey grounds, and surface is spoken for elsewhere. */
.card-grid:not(.card-grid--steps) {
  /* overflow and the bottom rule belonged to the shared-hairline trick:
     the cells were pulled one pixel left so the outer edge had none. */
  overflow: visible;
  border-bottom: 0;
}
.card-grid:not(.card-grid--steps) > .card-grid__inner {
  gap: var(--wp--preset--spacing--50);
  margin-left: 0;
}
/* A LITTLE LIFT [Emilie 6 okt]. Two layers, which is what makes a shadow
   read as a card rather than as a blur: a tight one that darkens the edge
   and keeps the border from looking drawn on, and a wide soft one that
   does the lifting.

   THE COLOUR IS THE PALETTE'S GRAPHITE, not black. Black over white goes
   grey and reads cold against ink that is blue-grey; mixing the page's
   own dark keeps the shadow the same temperature as everything else.

   theme.json publishes no shadow presets and sets defaultPresets to
   false, so there is no token to reach for and nothing in the editor
   offers one. This is the only shadow on the site besides the focus ring.

   TWO GRIDS, ONE CARD [Emilie 6 okt]. The process page builds the same
   three scenarios out of .feature-grid instead, with a label, a title, a
   paragraph and a consequence, and asked to look the same. One rule with
   two selectors rather than a copy, so the border, the radius and the
   shadow cannot drift apart later.

   The condition on the second is the one the file already uses for this
   grid: a feature grid carrying a consequence. It is one grid on the
   whole site, counted, and every other feature grid keeps its hairline
   over the top of each column.

   THE FLOW CARDS TOO [Emilie 7 okt], and the platform page's
   .feature-grid--cards, which draw the flow card. This rule is the only
   place a card's border, radius and shadow are described. What stays on
   .flow-card is what is not shared: the fixed width, the scroll snap and
   the tighter padding a 300px card in a scroller needs.

   AND THE DIRECTION TABLE [Emilie 6 nov], the process page's panel under
   the scenario cards, so the two read as the same kind of card. Only that
   panel: the other panels sit on coloured grounds and beds and were not
   asked for. Matched on .dir-rows, which nothing else on the site carries. */
.card-grid:not(.card-grid--steps) .card-grid__item,
.feature-grid:has(.consequence):not(.feature-grid--steps) > .feature-col,
.feature-grid--cards > .feature-col,
.panel:has(.dir-rows),
.flow-card {
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  box-shadow:
    0 1px 2px color-mix(in srgb, var(--wp--preset--color--graphite) 5%, transparent),
    0 10px 24px -6px color-mix(in srgb, var(--wp--preset--color--graphite) 9%, transparent);
}
/* HOVER LIFTS A CARD, OR ZOOMS ITS PICTURE [19 okt]. v.1: hover lifts 3px
   or zooms a picture 3%, over 200ms. A card with a picture zooms the
   picture inside a frame that stays put; a card without one lifts.

   ONLY A CARD THAT IS A LINK. Everything hangs off the anchor, the same
   as the title's underline does, so a card without one stays still and
   promises no target it lacks. Two cards carry a link: the flow card from
   its title and the media card from its value. A third linked card goes
   in this list, not in a modifier on its own rule.

   The flow row pads 6px above its cards, which is room for the 3px. */
.flow-card,
.media-card__image img {
  transition: transform var(--dur-hover) var(--ease);
}
.flow-card:has(.flow-card__title a:hover) {
  transform: var(--hover-lift);
}
/* The frame clips the zoom to the picture's own corners. */
.media-card:has(.media-card__value a) .media-card__image {
  overflow: hidden;
  border-radius: var(--radius-card);
}
.media-card:has(.media-card__value a:hover) .media-card__image img {
  transform: var(--hover-zoom);
}
/* The gap between the cards, the same on both grids. The feature grid's
   own 48px row gap and 32 to 64 column gap belong to columns divided by
   a rule, not to boxes standing apart. */
.feature-grid:has(.consequence):not(.feature-grid--steps) {
  gap: var(--wp--preset--spacing--50);
}
/* The flow cards' 16px, the gap of the row they stand in on the front
   page. After .feature-grid, which sets a gap of its own at the same
   weight. */
.feature-grid--cards {
  gap: var(--wp--preset--spacing--40);
  /* The grid is the container its own cards ask about; see below. */
  container-type: inline-size;
}
/* A LONE CARD ON THE LAST ROW STANDS CENTRED [Emilie 13 okt], one card
   wide, under the gap between the cards above it. Three cards in two
   columns on the process page, four in three on the platform page. In a
   single column there is nothing to centre under and the rule is off.

   The grid's auto-fit decides the column count, and CSS cannot ask a grid
   how many columns it drew, so the queries ask the width instead. The
   breakpoints are the grid's own arithmetic: n tracks of 280px and n - 1
   gaps of 16px. Change the 280 in .feature-grid or the gap above and
   these numbers move with them; a container query cannot read var().

   The card spans the whole row so justify-self can centre it, and its
   width is one track's: the row less its gaps, divided by the columns. */
@container (min-width: 576px) and (max-width: 871.98px) {
  .feature-grid--cards > .feature-col:last-child:nth-child(2n + 1) {
    grid-column: 1 / -1;
    justify-self: center;
    width: calc((100% - 16px) / 2);
  }
}
@container (min-width: 872px) and (max-width: 1167.98px) {
  .feature-grid--cards > .feature-col:last-child:nth-child(3n + 1) {
    grid-column: 1 / -1;
    justify-self: center;
    width: calc((100% - 2 * 16px) / 3);
  }
}
/* ONE GREY FOR EVERY RULE IN THE SET [Emilie 6 okt], the top rule
   included. A graphite top rule would put a near black line across three
   cells whose own dividers are hairline. The numbering says it is a
   sequence; the line does not have to.

   Each ground has one grey: hairline on the light, and hairline-dark on
   the dark through the rule further down.

   The set still has no bottom rule. That is the sequence ending open,
   not a colour. */
.card-grid--steps {
  border-bottom: 0;
}
.card-grid__title {
  margin: var(--wp--preset--spacing--40) 0 0;
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.25;
  letter-spacing: -0.01em;
  text-wrap: pretty;
}
.card-grid--steps .card-grid__title {
  max-width: 16ch;
  text-wrap: balance;
}
.card-grid__text {
  /* flex: 1 so the consequence block below sits on the bottom edge of
     every cell whatever the text above it runs to. */
  flex: 1;
  max-width: 42ch;
  margin: var(--wp--preset--spacing--40) 0 0;
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}

/* The hero panel's diagram: one transaction from the CRM through Syncify
   to both systems. The dash that runs along the paths is further down;
   /erp-byte/ draws no flow paths and stays still.

   THE CENTRE CARRIES THE MARK, as the design does: the official
   assets/logo/syncify_symbol_white.svg, placed as an image in the hub.
   Guardrail 6 rules out drawing the mark, not placing its file. */
.flow-diagram {
  display: block;
  width: 100%;
  height: auto;
}
.flow-diagram__path {
  fill: none;
  stroke: var(--wp--preset--color--hairline);
  stroke-width: 1.5;
}
.flow-diagram__hub {
  fill: var(--wp--preset--color--graphite);
}
.flow-diagram__ring,
.flow-diagram__node {
  fill: var(--wp--preset--color--ground);
  stroke: var(--wp--preset--color--hairline);
  stroke-width: 1.5;
}
.flow-diagram__ring {
  fill: none;
}
/* The system's icon inside its node. Label ink, never the signal colour:
   cyan is for data that moves, and a node is where it stands still. */
.flow-diagram__icon {
  color: var(--panel-ink, var(--wp--preset--color--text-strong));
}
/* The one node that deviates, drawn in the darkened deviation colour.
   This is the theme's rule kept, not broken: the signal colour belongs to
   data that deviates, and that is exactly what this ring marks. */
.flow-diagram__mark {
  fill: none;
  stroke: var(--status-deviation);
  stroke-width: 1.5;
}
/* ------------------------------------------------------------------
   The dash that travels along a path. [Emilie 9 okt]

   ONE KEYFRAME FOR EVERY PATH, however long it is. Each flow path
   declares pathLength="100", which tells the browser to treat its own
   length as a hundred units, so a dash array written in those units is
   the same fraction of a short path and a long one. Without it the fan's
   eight curves are eight different lengths and the dash would be a
   different size on each.

   THE GEOMETRY. dasharray 7 100 is a seven unit dash and a hundred unit
   gap, so only one dash is ever on the path. dashoffset shifts the
   pattern backwards, so a dash with offset O sits from -O to -O+7 along
   the path.

   IT RUNS THE WHOLE PATH AND INTO THE HUB [Emilie 9 okt]. The sweep goes
   from entirely before the start to entirely past the end, and the path's
   own extent does the clipping: a dash spanning -3 to 4 is drawn only
   where it overlaps the path, so it grows out of the start and shrinks
   into the end without a single line asking it to. The hub circle and the
   node circles are painted AFTER these paths, so what is left of the dash
   at either end is covered by them. It arrives inside Syncify rather than
   stopping outside it.

   THE CROWDING IS FIXED IN TIME, NOT IN SPACE. Two earlier attempts fixed
   it in space, and both were wrong. Stopping the dash short of the hub
   left it dissolving in open air; fading it in and out read as a
   rendering fault. The real fault was never where the dashes stopped but
   WHEN they arrived: the eight curves converge, and at 400ms apart in a
   3200ms cycle all four on a side sat inside 37 per cent of the cycle, so
   two or three were in the converging stretch together. Spread to a
   quarter cycle apart they cannot be: 25 per cent apart means no two are
   ever within the last 15 per cent at the same time. One dash reaches the
   mark at a time, which is what the figure is trying to say anyway.

   A QUIET FIFTH OF THE CYCLE. The travel finishes at 80 per cent and the
   dash waits off the end for the rest, so a path is empty for a moment
   between passes instead of carrying something at all times. With the
   four spread a quarter apart, the hub takes one arrival, then has room
   before the next.

   stroke-opacity 0 at rest, and it is not a fade: the keyframes set it to
   1 at zero per cent and never move it again. It exists so that a page
   where these never animate, which today means a page without scripting,
   draws nothing rather than parking a dash on the start of every path.
   Opacity rather than a zero length dash, because a round cap on a zero
   length dash is drawn as a dot and would leave a bead on all sixteen.

   backwards fill, because the delay staggers the paths and an undelayed
   element shows its own value meanwhile: dashoffset 0 would park a dash
   at the start of five paths for the first second and a half. backwards
   applies the from frame during the wait instead.

   THE DEVIATION INK, darker still [Emilie 9 okt]. A moving dash says
   data is flowing here, which makes it a graphic that carries meaning,
   and WCAG 1.4.11 asks 3:1 of those. The signal colour measures 2.48:1
   against the page and is ruled out on that alone. The first build used
   --status-deviation at 3.6:1; this is --status-deviation-ink, the same
   design system family one step down, measured 6.16:1 against white.

   A SHORTER DASH NEEDS MORE INK, which is why the two changed together.
   Twelve units of 3.6:1 and seven units of 6.16:1 carry about the same
   weight on the page; seven units of the lighter value read as a smudge.
   Do not swap it back for being brighter.

   linear, not an ease. The dash is a position, the same argument the
   transaction log's rail is written under.

   NO PAUSE CONTROL [Mattias 14 okt]. The motion on the site is small, so
   every loop runs without one. That fails WCAG 2.2.2 by decision; see
   CLAUDE.md. prefers-reduced-motion still stops it below.
   ------------------------------------------------------------------ */
.flow-diagram__flow {
  fill: none;
  stroke: var(--status-deviation-ink);
  stroke-width: 2.5;
  stroke-linecap: round;
  stroke-dasharray: 7 100;
  stroke-opacity: 0;
  animation: syncify-flow-dash 3.2s linear infinite backwards;
  animation-delay: var(--flow-start, 0ms);
}
/* Offset 7 puts the dash at -7 to 0, entirely before the path; -100 puts
   it at 100 to 107, entirely past it. Everything between is drawn only
   where it overlaps, which is what makes it grow out of the start and
   shrink into the end. The last fifth is the rest. */
@keyframes syncify-flow-dash {
  0%   { stroke-dashoffset: 7; stroke-opacity: 1; }
  80%  { stroke-dashoffset: -100; stroke-opacity: 1; }
  100% { stroke-dashoffset: -100; stroke-opacity: 1; }
}

/* The hub answers the arrivals. One pulse per cycle on the ring only; the
   filled circle and the mark inside it hold still, because the mark is
   the logotype and a logotype that breathes is a logotype being drawn.

   ONLY WHERE SOMETHING ARRIVES. /erp-byte/ draws a ring with no dashes,
   and that panel stays still by decision [Emilie 9 okt]. A ring that
   pulses with nothing reaching it answers nothing. :where() keeps the
   weight at one class, so the reduced motion rule below still wins. */
:where(.flow-diagram:has(.flow-diagram__flow)) .flow-diagram__ring {
  animation: syncify-flow-hub 3.2s var(--ease, ease-in-out) infinite;
}
@keyframes syncify-flow-hub {
  0%, 40%, 100% { opacity: 1; }
  20%           { opacity: 0.35; }
}

/* REDUCED MOTION IS THE DRAWING AT REST, and here that means the dash is
   gone rather than stopped. A dash frozen half way along a curve reads as
   a mark on the diagram rather than as motion that stopped. The global
   block up top would shorten these to 0.01ms and let the fill mode land
   them somewhere; said outright here instead, so there is one resting
   picture to check. The dash rests at opacity 0, so taking the animation
   away leaves nothing drawn. */
@media (prefers-reduced-motion: reduce) {
  .flow-diagram__flow,
  .flow-diagram__ring {
    animation: none;
  }
}
/* The node names. THE PANEL'S INK, not the page's, so the labels follow
   whatever surface the panel that holds the figure is on, the same way
   the panel rows read it. */
.flow-diagram__label {
  fill: var(--panel-ink, var(--wp--preset--color--text-strong));
  font-family: inherit;
  font-size: 14px;
}

/* ------------------------------------------------------------------
   Reconciliation page.

   THE HERO PANEL MOVES, 2 okt. The design runs a rail along the three
   steps on a six second loop and lights each step as it arrives, the
   same figure as the process page's transaction log. It uses the
   theme's keyframes rather than its own: see syncify-rail.

   Almost nothing new. The hero is the film hero again, the panels are
   .panel, the scenario and step cells are .card-grid, the record list is
   .split-rows and the closing band is .section--contact. What this block
   adds is the dark variant of the card grid and the two column system
   list with its category labels.
   ------------------------------------------------------------------ */

/* The card grid on a dark band: the hairlines change, nothing else. */
.section--dark .card-grid {
  border-bottom-color: var(--hairline-color-dark);
}
.section--dark .card-grid__item {
  border-top-color: var(--hairline-color-dark);
  border-left-color: var(--hairline-color-dark);
}
.section--dark .card-grid__text {
  color: var(--text-muted-on-dark);
}

/* The systems, two to a row: a slot for the mark and the kind of system
   under it.

   THE MARKS AND THE NAMES ARE OUT, guardrail 7, until the control matrix
   clears. THE CATEGORIES STAY: "Affärssystem" and "Betalväxel" name a
   kind of system and not a company, so nothing waits on them. That is
   why this section still says something, where the connectors page's
   list could not. */
/* No rules, 6 okt. The space between the cells and the labels carry the
   grid's shape, not a line above and below each cell. */
.system-cells {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  margin-top: clamp(40px, 5vw, 64px);
}
.system-cells > * {
  margin-block: 0;
}
/* The kind is centred under the mark [Emilie 26 okt]. The slot centres its
   mark, so a kind set flush left read as belonging to the cell rather than
   to the system above it. The cell shrinks to its widest child, the 160px
   slot as a rule, and both are centred in that. */
.system-cell {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-self: start;
  gap: var(--wp--preset--spacing--40);
  padding: var(--wp--preset--spacing--60) var(--wp--preset--spacing--50) var(--wp--preset--spacing--60) 0;
}
.system-cell__slot {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 160px;
  max-width: 100%;
  height: 40px;
  border: 1px dashed var(--wp--preset--color--hairline);
  border-radius: var(--radius-button);
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  letter-spacing: 0.08em;
  text-transform: uppercase;
}
.system-cell__kind {
  margin: 0;
  text-align: center;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
@media (max-width: 600px) {
  .system-cells {
    grid-template-columns: 1fr;
  }
}

/* The records that flow: a short label and a line about it. Not
   .split-rows, whose title is a rubrik and sized for a full width band;
   these sit in half a band and are labels, not headings. */
.record-rows {
  display: flex;
  flex-direction: column;
  margin: clamp(32px, 4vw, 56px) 0 0;
}
.record-row {
  display: grid;
  grid-template-columns: minmax(0, 11ch) minmax(0, 1fr);
  gap: var(--wp--preset--spacing--20) var(--wp--preset--spacing--60);
  padding-block: var(--wp--preset--spacing--40);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.record-row > * {
  margin: 0;
}
.record-row__title {
  font-size: 15px;
  font-weight: 500;
  color: var(--wp--preset--color--text-strong);
}
.record-row__text {
  font-size: 15px;
  line-height: 1.6;
  color: var(--panel-quiet, var(--wp--preset--color--text-body));
  text-wrap: pretty;
}
@media (max-width: 480px) {
  .record-row {
    grid-template-columns: 1fr;
  }
}

/* ------------------------------------------------------------------
   Integration page.

   The template that carries 301 posts. The hero, a band for each of the
   post's own blocks, and the form. See "Integration pair" and
   "Integration hub" below for what each kind of page does with its
   blocks.

   NARROWER THAN THE REST OF THE SITE. The design sets its content to
   1080 where the marketing pages run to 1440, and that is right for a
   page whose body is one column of editor text. It is set by redefining
   --container-max on the main region, so .container and every edge
   calculation that reads it follow without a second class.
   ------------------------------------------------------------------ */
.site-main--integration {
  --container-max: 1080px;
  /* The figure runs the height of the page, so the region that carries it
     is the one the figure has to cover, and it is pulled up under the
     transparent header so the figure starts at the top of the window and
     not under a 72 pixel band of nothing. The hero gives the height back
     as padding, the same pair .section--hero uses. */
  position: relative;
  overflow: hidden;
  margin-top: calc(var(--header-height) * -1);
}
.section--integration-hero {
  padding-top: calc(var(--section-pad) + var(--header-height));
}


/* The flow figure, entering behind the heading from the top right.

   MATTED ON WHITE, so this is flow.webp and not one of the two dark
   mattes. The ground here is the page's own white and that is the one
   the file was encoded against.

   TOP TO BOTTOM, AND THE SURFACES DECIDE WHAT COVERS IT. Every other
   ribbon in the theme is kept off the text by hiding it. This one runs
   the height of the page, so the rule is the other way round: anything
   that cannot be read on it brings its own surface.

   Measured from the file rather than from a screenshot, so the worst
   case holds however the figure is scaled. Its darkest pixel is
   rgb(5, 114, 143); at 0.55 over the ground that lands on rgb(115, 175, 191),
   where the strong ink reads 5.13:1 and the body ink 2.34:1.

   SO: strong ink may cross it and body ink may not. Checked in the page
   at 1600, 1440, 1200 and 1021, walking every text box that overlaps the
   figure: the navigation, the closing band and the footer sit on their
   own surfaces, the three columns sit on the white the block already
   paints, and the one thing left uncovered is the outline button in the
   flow band, which is strong ink and clears both 4.5:1 for its label and
   3:1 for its one pixel border. Add a surface to anything body coloured
   that moves into this column later.

   The closing dark band's own surface covers the figure there. The figure
   is matted on white and would paint a pale pillar on graphite if it
   showed through; the graphite matte exists as flow-dark.webp if that band
   should ever carry one of its own. */
.site-main--integration::before {
  content: "";
  position: absolute;
  /* BEHIND THE CONTENT, not in front of it. A positioned pseudo element at
     z-index 0 paints over the backgrounds of the static blocks around it,
     which would put the figure on top of the words. Negative puts it back
     where a background belongs, and then every surface that wants to cover
     it only has to have one. */
  z-index: -1;
  inset-block: 0;
  right: max(var(--gutter), calc((100% - var(--container-max)) / 2));
  width: clamp(220px, 26vw, 360px);
  /* STRETCHED TO THE PAGE, not drawn at its own 440 by 4379. Running top to
     bottom is the point, and the figure is soft vertical flow with no
     detail to distort, so scaling it along its own direction costs
     nothing a reader can see. */
  background: url("assets/media/flow.webp?v=2") center / 100% 100% no-repeat;
  opacity: 0.55;
  pointer-events: none;
}
/* Below the width where the text columns stop clearing the figure, the
   figure goes. Same reasoning as the three ribbons before it: body
   coloured text cannot cross it at any opacity that leaves a figure to
   look at, so the answer is text that does not cross it. */
@media (max-width: 1020px) {
  .site-main--integration::before {
    display: none;
  }
}

/* The heading. Two names and the word between them, with the pair set in
   the heavier weight so the eye lands on the systems and not on the
   verb. */
.integration-heading {
  margin: 0;
  max-width: 20ch;
  text-wrap: balance;
}
.integration-heading b {
  font-weight: 400;
}

/* The row under the heading: the two marks, and the way in. They sit
   side by side while there is room for both and stack when there is
   not. */
.pair-row {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 360px), 1fr));
  align-items: center;
  justify-items: center;
  gap: var(--wp--preset--spacing--60);
  margin-top: clamp(40px, 5vw, 64px);
}
.pair-row > * {
  margin-block: 0;
}

/* The pair itself: a box, a rule, the Syncify mark, a rule, a box.

   THE TWO MARKS ARE THE POST'S OWN, out of the media library, which is
   where the 301 pages have always kept them. The theme ships none of
   them. Its own mark between them is referenced and never drawn, per
   guardrail 6. */
.pair-logos {
  display: flex;
  align-items: center;
  justify-content: center;
  margin: 0;
  max-width: 100%;
}
.pair-logos__slot {
  flex: none;
  display: flex;
  align-items: center;
  justify-content: center;
  box-sizing: border-box;
  width: 120px;
  height: 120px;
  padding: var(--wp--preset--spacing--30);
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--ground);
}
.pair-logos__img {
  max-width: 100%;
  max-height: 100%;
  width: auto;
  height: auto;
  object-fit: contain;
}
/* A BOX WITH A MARK IN IT IS THE MARK [Emilie 12 nov]: no border and no
   padding, so the logotype is as large as the open box beside it. The box
   stays drawn only while it is empty, the plus or a missing image. Three
   classes so it also beats the card size's padding in integrations.css. */
.pair-logos .pair-logos__slot:has(> .pair-logos__img) {
  padding: 0;
  border: 0;
}
.pair-logos__rule {
  flex: none;
  width: clamp(24px, 4vw, 56px);
  height: 1px;
  background: var(--wp--preset--color--hairline);
}
.pair-logos__mark {
  flex: none;
  display: block;
  width: 28px;
  height: 28px;
  margin-inline: var(--wp--preset--spacing--30);
}
/* ONE ROW AT EVERY WIDTH [11 Nov, pair design]. Until then the row turned
   on its end under 420, because at 320 two 120 pixel boxes, two rules and
   the mark need 344 pixels and the column has 280. Now the boxes give way
   first, down to 88 at 320 (the design says 96 under 360, which still
   overflows at 320 by 12), and the rules shrink to 12. At 320 the row is
   88 + 12 + 52 + 12 + 88 = 252. */
@media (max-width: 480px) {
  .pair-logos__slot {
    width: clamp(88px, 27vw, 120px);
    height: clamp(88px, 27vw, 120px);
  }
  .pair-logos__rule {
    flex: 0 1 clamp(24px, 4vw, 56px);
    min-width: 12px;
  }
}

/* ------------------------------------------------------------------
   Integration pair.

   The pair design [11 Nov, "Integrera Fortnox Billogram"]: the hero, the
   three benefit columns, the "Flow" band and the form. The columns and
   the flow band are the post's own acf/threecolumns and acf/centeredtext,
   laid out here by the band single-integration.php puts each in.
   ------------------------------------------------------------------ */

/* THE COLUMNS. Straight under the hero: its bottom padding is the gap, and
   the top rule sits exactly where it ends.

   THE LINES ARE DRAWN BY THE COLUMNS, as on the pair cards: the grid has the
   top and left rule, each column its right and bottom. The line between two
   columns is single at three, two and one across, and when three wrap to
   two the empty cell has no frame. The block's own 1px gap over a hairline
   backing would fill that cell with rule colour.

   The surface is the ground, so the columns cover the flow figure and the
   figure shows above and below them. Only on this template; the block is
   shared. */
.section--integration-threecolumns {
  padding-block: 0;
}
.section--integration-threecolumns .block--threecolumns {
  margin-block: 0;
}
.section--integration-threecolumns .block--threecolumns__grid {
  gap: 0;
  border: 0;
  border-top: 1px solid var(--wp--preset--color--hairline);
  border-left: 1px solid var(--wp--preset--color--hairline);
  background: none;
}
/* Three classes, because the block's own padding rules are two and its file
   loads after this one. */
.section--integration-threecolumns .block--threecolumns .block--threecolumns__column {
  padding: var(--wp--preset--spacing--60) clamp(20px, 2.5vw, 40px);
  border-right: 1px solid var(--wp--preset--color--hairline);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
  background: var(--wp--preset--color--ground);
}
/* The columns' "Kom igång nu" is drawn in the hero instead, read from the
   same field by single-integration.php. Hidden here, not removed: the
   block is shared and keeps its button everywhere else. */
.section--integration-threecolumns .block--threecolumns > .buttons {
  display: none;
}
/* The column headings are h2 in the stored text (Theme Settings), so they
   are set by place and not by element. Light, as the design draws them. */
.section--integration-threecolumns .block--threecolumns__column :is(h2, h3) {
  margin: 0 0 var(--wp--preset--spacing--40);
  font-size: clamp(1.125rem, 1.5vw, 1.375rem);
  font-weight: 300;
  line-height: 1.12;
  letter-spacing: -0.02em;
  text-wrap: balance;
}
.section--integration-threecolumns .block--threecolumns__column p {
  max-width: 42ch;
  color: var(--wp--preset--color--text-body);
  font-size: 0.9375rem;
  line-height: 1.7;
  text-wrap: pretty;
}

/* THE FLOW BAND. The centred text block, uncentred: heading and text on
   the left, the button alone on the right, level with the last line and
   straight under the hero's "Kom igång nu". The block's two children are
   the grid's two columns.

   THE BUTTON IS FILLED HERE whichever of the block's two button fields
   holds it. In the stored data "Kontakta oss" is button_2, which the block
   draws as the outline button; the design draws it as the primary one. */
.section--integration-centeredtext .block--centeredtext {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 360px), 1fr));
  align-items: end;
  justify-items: center;
  gap: var(--wp--preset--spacing--60);
  margin-block: 0;
  text-align: left;
}
.section--integration-centeredtext .block--centeredtext__text {
  justify-self: stretch;
  max-width: none;
  margin-inline: 0;
}
.section--integration-centeredtext .block--centeredtext__text :is(h2, h3) {
  max-width: 22ch;
}
.section--integration-centeredtext .block--centeredtext__text p {
  max-width: 60ch;
  color: var(--wp--preset--color--text-body);
}
.section--integration-centeredtext .block--centeredtext .buttons {
  margin-top: 0;
}
.section--integration-centeredtext .block--centeredtext .button--outline {
  background: var(--wp--preset--color--graphite);
  color: var(--wp--preset--color--text-on-dark);
}
.section--integration-centeredtext .block--centeredtext .button--outline:hover {
  background: var(--wp--preset--color--graphite-deep);
  border-color: var(--wp--preset--color--graphite-deep);
}

/* ------------------------------------------------------------------
   Integration hub.

   The 38 system pages [Emilie 11 nov, design handoff "Integrera
   Billogram"]. single-integration.php puts the post's excerpt in the hero
   and gives each of its other blocks a band: the list of pairs, then the
   two image and text blocks. Colours and type are the theme's tokens, not
   the handoff's hex values [Emilie 11 nov], and the flow figure is the
   template's own, gone under 1020 as before.
   ------------------------------------------------------------------ */

/* The hero: the excerpt and the way in on the left, the marks centred on
   the right. Stacks under about 760, text first. */
.pair-row--hub > .pair-row__text {
  justify-self: stretch;
}
.pair-row__text .block {
  margin-block: 0;
}
.pair-row__text .lead {
  margin-top: 0;
}

/* The open slot: whichever system the visitor has. A typographic plus at
   the size of the icon the design draws, in the strong ink. */
.pair-logos__plus {
  color: var(--wp--preset--color--text-strong);
  font-size: 28px;
  font-weight: 300;
  line-height: 1;
}

/* The blocks carry their own bottom margin for a page where they follow
   each other; here each has a band and the band's padding is the space. */
.section--integration-band .block {
  margin-block: 0;
}
/* The list follows the hero straight on, as the design draws it. */
.section--integration-integrations {
  padding-top: 0;
}
.integration-systems__heading {
  margin: 0 0 var(--wp--preset--spacing--60);
}

/* Both image and text variants lay out on the hero's grid on this page,
   not on the block's own hairline split. */
.section--integration-band .block--imagetext {
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 360px), 1fr));
  gap: clamp(32px, 5vw, 64px);
}
/* Three classes deep on purpose: the block's own sides rule is two, and
   its file loads after this one. */
.section--integration-band .block--imagetext .block--imagetext__media,
.section--integration-band .block--imagetext .block--imagetext__body {
  padding-inline: 0;
  border-inline: 0;
}

/* THE LOGOS VARIANT, "Hur fungerar". The design draws the text on the left
   and the button alone on the right, level with the last line, and no
   logos: the hero above already shows the system. The body is unwrapped
   so its text and its button become the two columns; the editor's logos
   stay in the post and are not drawn on this page. */
.section--integration-band .block--imagetext--logos {
  align-items: end;
  justify-items: center;
}
.section--integration-band .block--imagetext--logos .block--imagetext__body {
  display: contents;
}
.section--integration-band .block--imagetext--logos .block--imagetext__text {
  justify-self: stretch;
}
.section--integration-band .block--imagetext--logos .block--imagetext__body .buttons {
  margin-top: 0;
}
.section--integration-band .block--imagetext--logos .block--imagetext__media {
  display: none;
}

/* THE IMAGE VARIANT, "Varför". A hairline over the band, the image at 4:3
   on the card radius. Which side it sits on is still the block's
   image_right field. */
.section--integration-band:has(.block--imagetext__image) {
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.section--integration-band .block--imagetext:has(.block--imagetext__image) {
  align-items: center;
}
.section--integration-band .block--imagetext__image {
  aspect-ratio: 4 / 3;
  object-fit: cover;
  border-radius: var(--radius-card);
}

/* "Skapa ett flow", the dialog behind the pair cards' first button.

   THE DIALOG IS THE VEIL, the panel sits in it. That makes a click on the
   dialog element itself a click outside the panel, which is how
   flow-dialog.js tells the backdrop from the form, and lets a panel taller
   than the window scroll inside the veil instead of off the page.

   The veil is graphite deep at 60 percent, the handoff's value expressed
   through the token. */
.flow-dialog {
  position: fixed;
  inset: 0;
  width: 100%;
  height: 100%;
  max-width: none;
  max-height: none;
  margin: 0;
  padding: clamp(16px, 6vh, 80px) var(--gutter);
  border: 0;
  background: color-mix(in srgb, var(--wp--preset--color--graphite-deep) 60%, transparent);
  overflow-y: auto;
  overscroll-behavior: contain;
}
.flow-dialog::backdrop {
  background: transparent;
}
/* The page behind does not scroll while the dialog is open. */
html:has(.flow-dialog[open]) {
  overflow: hidden;
}
.flow-dialog__panel {
  display: flex;
  flex-direction: column;
  gap: 28px;
  max-width: 560px;
  margin-inline: auto;
  padding: clamp(24px, 4vw, 40px);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--ground);
}
.flow-dialog__head {
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: var(--wp--preset--spacing--40);
}
.flow-dialog__title {
  margin: 0;
  font-size: 1.5rem;
  font-weight: 400;
  line-height: 1.2;
}
.flow-dialog__system {
  margin: var(--wp--preset--spacing--10) 0 0;
  color: var(--wp--preset--color--text-body);
  font-size: 0.9375rem;
}
.flow-dialog__close {
  flex: none;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  margin: -10px -10px 0 0;
  padding: 0;
  border: 0;
  border-radius: var(--radius-button);
  background: transparent;
  color: var(--wp--preset--color--text-strong);
  cursor: pointer;
}
.flow-dialog__close:hover {
  background: var(--wp--preset--color--surface);
}
.flow-dialog__form,
.flow-dialog__actions {
  margin-top: 0;
}

/* ------------------------------------------------------------------
   Order to cash page.

   Seven bands, and most of them are parts the theme already has: the
   card grid from the ERP migration page, the stepped card grid from the
   reconciliation page, the white panel from the process page, the flow
   diagram from the ERP migration page, the system list from the process
   page, the closing band from the front page.

   What is new is the dark band that is not a hero and the rows that say
   which way each record goes.
   ------------------------------------------------------------------ */

/* The darkest band, as an ordinary section rather than a hero. The hero
   here is dark but not full height, so it takes this background instead
   of .section--hero and its film. */
.section--graphite-deep {
  background: var(--wp--preset--color--graphite-deep);
  --field-surface: var(--wp--preset--color--graphite-deep);
}

/* The flow figure over it, entering from the top right.

   flow-deep.webp, the matte made for graphite deep. Measured against
   that ground when it was encoded: ljus reaches 3.64:1, cyan 2.60:1 and
   teal 1.74:1, so ljus. Here it sits at the design's 0.45 rather than
   the 0.42 the connectors hero needed, because nothing crosses it: the
   words stop at the panel's left edge and the panel is opaque. */
.section--graphite-deep {
  position: relative;
  overflow: hidden;
}
.section--graphite-deep > .container {
  position: relative;
  z-index: 1;
}
.section--graphite-deep::before {
  content: "";
  position: absolute;
  z-index: 0;
  top: -120px;
  right: calc(var(--outside-container) - 60px);
  width: min(295px, 22vw);
  aspect-ratio: 440 / 4379;
  background: url("assets/media/flow-deep.webp?v=2") center top / 100% 100% no-repeat;
  opacity: 0.45;
  transform: rotate(12deg);
  pointer-events: none;
}
/* Below the width where the panel stops sitting beside the words, the
   figure would be behind the words instead of beside them. */
@media (max-width: 1020px) {
  .section--graphite-deep::before {
    display: none;
  }
}

/* Data on its way between two systems, as a chip.

   NOT A NEW COLOUR. This is the deviation ink and its tint, under a
   second name. The theme's rule is that cyan is carried by data that
   MOVES or DEVIATES, so both meanings are the signal colour's own, and
   the darkened value is the one that clears 4.5:1 as text. */
.chip--sync {
  border-color: var(--status-deviation-surface);
  background: var(--status-deviation-surface);
  color: var(--status-deviation-ink);
}

/* The records in the chain: what it is, what it carries, and which way
   it goes. Stacked rather than columned, because the direction is a
   third line and not a third column at the width this list sits in. */
.chain-rows {
  margin-top: clamp(32px, 4vw, 48px);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.chain-row {
  display: flex;
  flex-direction: column;
  gap: var(--wp--preset--spacing--10);
  padding-block: var(--wp--preset--spacing--40);
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.chain-row > * {
  margin-block: 0;
}
.chain-row__title {
  font-size: 15px;
  font-weight: 500;
  color: var(--panel-ink, var(--wp--preset--color--text-strong));
}
.chain-row__text {
  font-size: 14px;
  line-height: 1.6;
  color: var(--panel-quiet, var(--wp--preset--color--text-body));
  text-wrap: pretty;
}
.chain-row__dir {
  margin-top: var(--wp--preset--spacing--10);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--panel-quiet, var(--wp--preset--color--text-body));
}

/* The diagram panel follows the list past it, but only where there is a
   column beside it to follow. Below that it is just a panel. */
@media (min-width: 1021px) {
  .panel--follow {
    position: sticky;
    top: calc(var(--header-height) + var(--wp--preset--spacing--50));
  }
}

/* The small annotation on a diagram path: what travels along it. Body
   colour, because it annotates rather than names. */
.flow-diagram__note {
  fill: var(--panel-quiet, var(--wp--preset--color--text-body));
  font-family: inherit;
  font-size: 12px;
}
/* A dashed leader from a callout to the place in the figure it names
   [Emilie 16 okt, /artificial-intelligence/]. The notes' grey, so it reads
   as an annotation and never as one more flow: the flows are solid, and
   only data in motion is coloured. Butt caps, so the dashes stay square. */
.flow-diagram__lead {
  fill: none;
  stroke: var(--panel-quiet, var(--wp--preset--color--text-body));
  stroke-width: 1;
  stroke-dasharray: 3 4;
}

/* ------------------------------------------------------------------
   Transaction log, the process page's hero panel.

   A picture of a screen: window chrome, tabs, one transaction being
   followed through three steps, and the rows behind it, in the design
   file's own layout.

   LIGHT, LIKE EVERY PANEL [Emilie 14 okt], where the design draws it in
   graphite. The values are the panel's
   own: white for the card, surface for the chrome, the foot and the
   focus band, the light hairline for every rule, body ink for the quiet
   text. Measured on surface, the darker of the two: body ink 5.14:1, the
   status inks 5.2 and 5.5, the deviation ink 5.53.

   THE CYAN IS EARNED HERE. v.1 gives the signal colour to data that
   moves or deviates, and the rail is a transaction crossing three systems
   in front of you. Where it is TEXT, the transaction id, it is the
   deviation ink, because the signal colour itself is
   2.48:1 on white. The rail and the dots keep the signal colour; see
   ATT-GORA.md on graphic objects under 3:1.
   ------------------------------------------------------------------ */
.txlog {
  --txlog-chrome: var(--wp--preset--color--surface);
  --txlog-focus: var(--wp--preset--color--surface);
  --txlog-rule: var(--wp--preset--color--hairline);
  --txlog-quiet: var(--wp--preset--color--text-body);

  overflow: hidden;
  border: 1px solid var(--txlog-rule);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
  /* Tabular figures, because the whole panel is timestamps and ids and a
     column of them that does not line up reads as a different kind of
     thing than a log. */
  font-variant-numeric: tabular-nums;
}

/* The window bar. The three marks are the design's; they are what makes
   the panel read as a screenshot of a product rather than as a table. */
.txlog__chrome {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  padding: 9px 14px;
  border-bottom: 1px solid var(--txlog-rule);
  background: var(--txlog-chrome);
}
.txlog__dots {
  display: flex;
  gap: 5px;
}
.txlog__dots i {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: var(--txlog-rule);
}

.txlog__tabs {
  display: flex;
  gap: 18px;
  margin: 0;
  padding: 0 14px;
  border-bottom: 1px solid var(--txlog-rule);
  font-size: var(--wp--preset--font-size--mikro);
}
/* Spans and not buttons. Nothing filters here: the panel is an
   illustration of a product screen, and a control that does nothing is
   the fault the flow cards' arrow was removed for. */
.txlog__tab {
  padding: 10px 0 9px;
  color: var(--txlog-quiet);
}
.txlog__tab--on {
  color: var(--wp--preset--color--text-strong);
  font-weight: 500;
  box-shadow: inset 0 -1.5px 0 currentColor;
}

/* The transaction being followed. */
.txlog__focus {
  padding: 14px 14px 4px;
  border-bottom: 1px solid var(--txlog-rule);
  background: var(--txlog-focus);
}
.txlog__focus-title {
  margin: 0;
  font-size: 12.5px;
  font-weight: 500;
}
.txlog__id {
  color: var(--status-deviation-ink);
}

.txlog__track {
  position: relative;
  margin-top: 14px;
}
/* The rail stops a sixth short at each end, so it begins and ends under
   the first and last node rather than at the panel's edge. A sixth is half
   a column of three. */
.txlog__rail {
  position: absolute;
  top: 4px;
  left: 16.6667%;
  right: 16.6667%;
  height: 1px;
  background: var(--txlog-rule);
}
.txlog__rail--live {
  background: var(--signal-flow);
  transform-origin: left;
  /* linear, not --ease. The steps light at fractions of the cycle that
     assume the rail covers ground at a constant rate; eased, a dot filled
     1.2s after the line had gone past it. A progress line is a position,
     not a gesture. */
  animation: syncify-rail 6s linear infinite;
}

.txlog__steps {
  position: relative;
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  margin: 0;
  padding: 0;
  list-style: none;
}
.txlog__step {
  min-width: 0;
  padding: 0 4px;
  text-align: center;
  /* Each step lights as the rail reaches it and STAYS lit until the rail
     resets. One cycle, three keyframes, no delay; see syncify-step-1 for
     why not one keyframe and a delay.

     The lit points are the rail's own geometry rather than numbers picked
     to look right. The rail spans 16.6667 to 83.3333 per cent, the three
     steps stand at those two ends and at the midpoint between them, and
     the rail grows over the first 72 per cent of the cycle. So it arrives
     at each step at 0, 36 and 72 per cent. */
  animation: 6s linear infinite;
}
.txlog__step:nth-child(1) { animation-name: syncify-step-1; }
.txlog__step:nth-child(2) { animation-name: syncify-step-2; }
.txlog__step:nth-child(3) { animation-name: syncify-step-3; }
/* THE RING ROUND A STATUS DOT. The step row on ekonomisk-avstamning and
   the chain on order till betalning once drew the same mark and shared
   this ring; both are gone [16 nov], and the transaction log keeps it.

   Mixed from the dot's own colour rather than written as a value, so a
   dot that changes colour takes its ring with it. The shadow is outside
   the layout, so the node does not move. */
.txlog__node {
  box-shadow: 0 0 0 3px color-mix(in srgb, var(--signal-flow) 18%, transparent);
}

.txlog__node {
  display: block;
  width: 9px;
  height: 9px;
  margin: 0 auto 10px;
  border-radius: 50%;
  background: var(--signal-flow);
}
.txlog__step-name {
  display: block;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
}
.txlog__step-meta {
  display: block;
  font-size: var(--wp--preset--font-size--mikro);
  line-height: 1.5;
  color: var(--txlog-quiet);
}

/* The rows behind the one in focus. A real table: three columns of
   tabular data, with a caption that says it is an example. */
.txlog__table {
  width: 100%;
  border-collapse: collapse;
  font-size: var(--wp--preset--font-size--mikro);
  text-align: start;
}
.txlog__table th,
.txlog__table td {
  padding: 8px 14px;
  vertical-align: middle;
}
.txlog__table th {
  padding-block: 8px 6px;
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 400;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--txlog-quiet);
  text-align: start;
}
.txlog__table th:last-child,
.txlog__table td:last-child {
  text-align: end;
  white-space: nowrap;
}
/* The first column is sized to its content, so its heading has to be
   allowed to set that width rather than wrap inside it. */
.txlog__table th:first-child {
  white-space: nowrap;
}
.txlog__table tbody tr {
  border-top: 1px solid var(--txlog-rule);
}
.txlog__table td:first-child {
  width: 1%;
  white-space: nowrap;
}
.txlog__ref,
.txlog__time,
.txlog__what,
.txlog__way {
  display: block;
  line-height: 1.45;
}
.txlog__time,
.txlog__way {
  font-size: var(--wp--preset--font-size--mikro);
  color: var(--txlog-quiet);
}
/* The object line is the only thing here that can be long enough to need
   cutting, and the column it sits in is the one that can give. */
.txlog__what {
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}

.txlog__status {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  font-size: var(--wp--preset--font-size--mikro);
}
.txlog__status-dot {
  width: 6px;
  height: 6px;
  border-radius: 50%;
  background: currentColor;
}
.txlog__status--ok {
  color: var(--status-ok);
}
.txlog__status--waiting {
  color: var(--status-warning);
}

.txlog__foot {
  display: flex;
  justify-content: space-between;
  gap: 12px;
  flex-wrap: wrap;
  margin: 0;
  padding: 9px 14px;
  border-top: 1px solid var(--txlog-rule);
  background: var(--txlog-chrome);
  font-size: var(--wp--preset--font-size--mikro);
  color: var(--txlog-quiet);
}

@keyframes syncify-rail {
  0%   { transform: scaleX(0); }
  72%  { transform: scaleX(1); }
  96%  { transform: scaleX(1); }
  100% { transform: scaleX(0); }
}
/* Dim until the rail arrives, lit from then to the end of the pass. The
   last two per cent is the reset, which happens to all three at once and
   with the rail, so it reads as the next transaction rather than as one
   step changing its mind.

   NAMED FOR THE THEME, NOT FOR THE LOG. The reconciliation page's hero
   panel is the same figure with different words, and a second copy of
   three keyframes is three places to fix the next time something here is
   wrong. The lit points are per cents of the cycle, not pixels, so any
   three step rail can use them.

   The design file writes these as ONE keyframe with delays, and that
   is the shape that makes the text flicker: a delay moves the whole
   cycle rather than the step inside it, so the last step fades out
   three and a half seconds into the next pass and dims while the rail
   runs towards it again. Do not copy it back. */
@keyframes syncify-step-1 {
  0%        { opacity: 0.25; }
  2%, 98%   { opacity: 1; }
  100%      { opacity: 0.25; }
}
@keyframes syncify-step-2 {
  0%, 34%   { opacity: 0.25; }
  36%, 98%  { opacity: 1; }
  100%      { opacity: 0.25; }
}
@keyframes syncify-step-3 {
  0%, 70%   { opacity: 0.25; }
  72%, 98%  { opacity: 1; }
  100%      { opacity: 0.25; }
}

/* ------------------------------------------------------------------
   The log standing up, below 720 [Emilie 22 okt; design review 7, N19].

   Narrow, the steps stood two and one with the rail gone, the status
   column was cut off at the panel's edge at 360 and 320, and the text
   was 9.5 to 12.5px. Same panel, same words, turned on its end: the
   steps run down a vertical rail, each table row stacks its three cells,
   and every word that carries the log is body size.

   CSS ONLY, so no page has to be written out again: the markup is the
   pattern's as it stands in /processer-erp-crm/.

   TWO SIZES. Body size (brod) for everything a reader reads as the log:
   the transaction in focus, the steps, the rows, the foot that says it
   is example data. The micro label (mikro, the design system's 12px for
   section names and metadata) for the three tab names, which picture
   the product screen and carry no data.
   The column heads leave the eye, below.

   THE RAIL TURNS, it does not go. Same two spans and the same keyframe
   percentages, on the vertical: the rows are one fraction each, so the
   first and last node stand half a row in from each end, as across, and
   the rail still reaches the middle step at 36 per cent and the last at
   72. The rail begins at the first node's middle, which is half a line
   down from the top of its row (--txlog-y), and ends at the same height
   in the last row.

   THE COLUMN HEADS ARE VISUALLY HIDDEN, not removed. Stacked, the three
   cells no longer stand under them, and a head over nothing is noise;
   each value names its own kind (an id, a time, an arrow, a status dot
   and word). The table is still a table to a screen reader, with its
   heads, in Chrome; see ATT-GORA for Safari.

   REDUCED MOTION rests where the wide one does, on the last keyframe:
   the global block lands every animation on 100%. That is the fault
   recorded as N2 in the 21 okt review (rail at zero, steps dimmed), not
   fixed here, so the two layouts rest alike.
   ------------------------------------------------------------------ */
@media (max-width: 719.98px) {
  .txlog {
    --txlog-y: 0.75em;
  }
  .txlog__tabs {
    font-size: var(--wp--preset--font-size--mikro);
  }
  .txlog__tabs {
    flex-wrap: wrap;
    column-gap: var(--wp--preset--spacing--40);
  }
  .txlog__focus-title,
  .txlog__track,
  .txlog__table,
  .txlog__time,
  .txlog__way,
  .txlog__status,
  .txlog__foot {
    font-size: var(--wp--preset--font-size--brod);
  }
  .txlog__focus {
    padding-bottom: 14px;
  }

  .txlog__rail {
    top: var(--txlog-y);
    bottom: calc((100% - 2 * var(--wp--preset--spacing--30)) / 3 - var(--txlog-y));
    left: 4px;
    right: auto;
    width: 1px;
    height: auto;
  }
  .txlog__rail--live {
    transform-origin: top;
    animation-name: syncify-rail-down;
  }
  .txlog__steps {
    grid-template-columns: minmax(0, 1fr);
    grid-auto-rows: 1fr;
    row-gap: var(--wp--preset--spacing--30);
  }
  .txlog__step {
    display: grid;
    grid-template-columns: 9px minmax(0, 1fr);
    column-gap: var(--wp--preset--spacing--40);
    align-content: start;
    padding: 0;
    line-height: 1.5;
    text-align: start;
  }
  .txlog__node {
    grid-row: span 2;
    margin: calc(var(--txlog-y) - 4.5px) 0 0;
  }
  .txlog__step-name,
  .txlog__step-meta {
    font-size: inherit;
    line-height: inherit;
  }

  .txlog__table,
  .txlog__table tbody {
    display: block;
  }
  .txlog__table thead {
    position: absolute;
    width: 1px;
    height: 1px;
    overflow: hidden;
    clip-path: inset(50%);
    white-space: nowrap;
  }
  .txlog__table tbody tr {
    display: flex;
    flex-direction: column;
    gap: 2px;
    padding: var(--wp--preset--spacing--30) 14px;
  }
  .txlog__table tbody tr:first-child {
    border-top: 0;
  }
  .txlog__table td,
  .txlog__table td:first-child,
  .txlog__table td:last-child {
    width: auto;
    padding: 0;
    text-align: start;
    white-space: normal;
  }
  .txlog__table td:first-child {
    display: flex;
    flex-wrap: wrap;
    column-gap: var(--wp--preset--spacing--20);
  }
  .txlog__what {
    overflow: visible;
    white-space: normal;
  }
  .txlog__status {
    margin-top: 2px;
  }
  .txlog__foot {
    row-gap: 2px;
  }
}
@keyframes syncify-rail-down {
  0%   { transform: scaleY(0); }
  72%  { transform: scaleY(1); }
  96%  { transform: scaleY(1); }
  100% { transform: scaleY(0); }
}

/* ------------------------------------------------------------------
   Portal illustration: a browser window showing Syncify Portal
   [Emilie 5 nov]. Built from the handoff design_handoff_portalillustrationer,
   whose inline styles are the source for every size and colour here. The
   process page's hero shows the run order in it.

   TWO VARIANTS FROM ONE MARKUP. The phone window is the default; from 960px
   of viewport the desktop window replaces it, which is the breakpoint the
   request names. The desktop window is 879px wide and 960 is the first width
   where the container (960 less two 4vw gutters, 883) holds it.

   A PICTURE, SO IT SCALES. Each window is zoomed down to the width it is
   given rather than reflowed, as the handoff asks: the phone window below
   402px, down to 320 with no sideways scroll (WCAG 1.4.10), and the desktop
   window below 879, which is every width where it stands beside the words
   [Emilie 5 nov]. zoom and not transform, because zoom
   also scales the box the layout sees, so nothing has to give back the
   height. tan(atan2()) turns the two lengths into a plain ratio, which
   calc() cannot do by division.

   EXCEPTIONS TO DECISIONS, ALL FROM THE HANDOFF, which calls itself final:
     - Text under 12px: the 9px kickers and the 10px step numbers, and every
       label once a window scales. Same kind of exception as
       .flow-stack [Emilie 22 okt, eftermiddag]: the figure is a picture
       with role="img", and the words are inside it.
     - Glass on the window [beslut användare]: the translucent gradient and
       the backdrop blur, against the design system's no glassmorphism.
   What it does NOT keep from the handoff: white. Every opaque white surface
   is the ground, #FAFAFA, since no background is #FFFFFF [Emilie 26 okt].

   No cyan. Nothing here moves.
   ------------------------------------------------------------------ */
.portal-figure {
  /* The handoff's tokens that the palette does not have. Kept here rather
     than in theme.json, so they are not offered as colours in the editor. */
  --portal-line-box: #C3CCD3;   /* hairline-strong in v.1 */
  --portal-shadow-far: 0 12px 28px rgba(27, 36, 44, 0.16);
  /* The desktop window's width, which differs per illustration: the run
     order is 879, the order record 696 (--records below). */
  --portal-desktop-width: 879px;

  container-type: inline-size;
  margin: 0;
}

.portal-window {
  width: 402px;
  overflow: hidden;
  border-radius: 12px;
  /* [beslut användare] Glass, against the design system. Thinner than the
     handoff's 0.8 to 0.62 white [Emilie 6 nov], 0.18 to 0.08, so the band
     and its flow figure show through the bar: at 0.8 the bar read as solid
     grey on graphite. The window lights are light for the same reason, see
     below.
     Only the bar is glass; the content under it is opaque. */
  background: linear-gradient(180deg, rgba(255, 255, 255, 0.18), rgba(255, 255, 255, 0.08));
  -webkit-backdrop-filter: blur(28px) saturate(160%);
  backdrop-filter: blur(28px) saturate(160%);
  box-shadow:
    0 0 0 1px rgba(27, 36, 44, 0.14),
    0 2px 4px rgba(27, 36, 44, 0.06),
    var(--portal-shadow-far);
  color: var(--wp--preset--color--text-strong);
  font-variant-numeric: tabular-nums;
  zoom: min(1, tan(atan2(100cqw, 402px)));
}

.portal-window__bar {
  display: flex;
  align-items: center;
  gap: 16px;
  height: 40px;
  padding: 0 14px;
  border-bottom: 1px solid rgba(27, 36, 44, 0.06);
  /* The glass's top edge catching the light. 0.9 in the handoff, made for
     its pale bar; on the thin glass it drew a hard white line along the
     top [Emilie 6 nov]. */
  box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.16);
}
.portal-window__lights {
  display: flex;
  flex: none;
  gap: 8px;
  width: 52px;
}
/* Light on the glass, not the handoff's three greys [Emilie 6 nov]: on a
   bar this thin the greys took the colour of the band behind and the third
   one vanished. The same falling ramp, in white. */
.portal-window__lights i {
  width: 12px;
  height: 12px;
  border-radius: 50%;
  background: rgba(255, 255, 255, 0.6);
}
.portal-window__lights i:nth-child(2) {
  background: rgba(255, 255, 255, 0.42);
}
.portal-window__lights i:nth-child(3) {
  background: rgba(255, 255, 255, 0.28);
}
.portal-window__address {
  flex: 1;
  padding-right: 10%;
}
.portal-window__field {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  height: 26px;
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: 7px;
  background: var(--wp--preset--color--surface);
  color: var(--wp--preset--color--text-body);
  font-size: 13px;
}
.portal-window__field span {
  color: var(--wp--preset--color--text-strong);
}

.portal-window__content {
  padding: 20px 20px 24px;
  background: var(--wp--preset--color--ground);
}
.portal-window__title {
  margin: 0;
  font-size: 22px;
  font-weight: 400;
  line-height: 1.3;
  letter-spacing: -0.01em;
  text-wrap: pretty;
}
/* The line under the title, on the windows that have one. */
.portal-window__lead {
  margin: 12px 0 0;
  color: var(--wp--preset--color--text-body);
  font-size: 13px;
  line-height: 1.6;
}

/* The diagram surface the run order, the parallel run and the portal flows
   stand on: light surface under three soft tints, from the handoff. */
.run-order,
.parallel-run,
.portal-flows {
  margin-top: 16px;
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  background-color: var(--wp--preset--color--surface);
  background-image:
    radial-gradient(ellipse 55% 70% at 22% 35%, rgba(195, 204, 211, 0.7), transparent 70%),
    radial-gradient(ellipse 50% 65% at 80% 70%, rgba(142, 154, 164, 0.28), transparent 70%),
    radial-gradient(ellipse 40% 50% at 55% 10%, rgba(217, 223, 227, 0.9), transparent 70%);
}
/* The run order board. The systems are posts from top to bottom, the steps
   run between them, and a hairline runs down the middle behind the steps. */
.run-order {
  --run-system: 34px;
  --run-gutter: 16px;

  position: relative;
  padding: 12px;
}
.run-order::before {
  content: "";
  position: absolute;
  top: 56px;
  bottom: 20px;
  left: 50%;
  width: 1px;
  background: var(--portal-line-box);
}
.run-order__system {
  position: absolute;
  top: 12px;
  bottom: 12px;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 6px;
  width: var(--run-system);
  padding-top: 10px;
  border: 1px solid var(--portal-line-box);
  border-radius: 10px;
  background: var(--wp--preset--color--ground);
}
.run-order__system--crm {
  left: 12px;
}
.run-order__system--erp {
  right: 12px;
}
.run-order__system svg {
  flex: none;
  color: var(--wp--preset--color--graphite);
}
.run-order__system-text,
.run-order__platform {
  display: flex;
  flex-direction: column;
  gap: 1px;
}
.run-order__kicker {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
}
/* The posts are 34px until the desktop window at 960px, and "CRM" at 12px
   with 0.18em ran 34.2px wide, over the post's border. The tracking gives,
   not the 12px floor. */
@media (max-width: 959.98px) {
  .run-order__system .run-order__kicker {
    letter-spacing: 0.06em;
  }
}
.run-order__name {
  font-size: 12px;
  font-weight: 500;
}
/* The phone's posts are too narrow for a name: the kicker says it. */
.run-order__system .run-order__name {
  display: none;
}

.run-order__lanes {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 4px;
  margin: 0 var(--run-system);
}
.run-order__platform {
  min-height: 44px;
  padding: 2px 0 0 calc(var(--run-gutter) + 4px);
}
.run-order__steps {
  display: flex;
  flex-direction: column;
  gap: 4px;
  margin: 0;
  padding: 0;
  list-style: none;
}
.run-order__item {
  position: relative;
  display: flex;
  align-items: center;
  gap: 8px;
  min-height: 28px;
  margin: 0 var(--run-gutter);
  padding: 3px 8px 3px 4px;
  border: 1px solid var(--portal-line-box);
  border-radius: 8px;
  background: var(--wp--preset--color--ground);
  font-size: 12px;
  line-height: 1.35;
}
.run-order__number {
  flex: none;
  display: grid;
  place-items: center;
  width: 20px;
  height: 20px;
  border-radius: 50%;
  background: var(--wp--preset--color--surface);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 500;
}
.run-order__text {
  flex: 1;
  min-width: 0;
}
.run-order__chevron {
  display: none;
  color: var(--wp--preset--color--text-body);
}

/* The arrow across the gutter: a line and a filled head, 7 by 8. Named by
   the system at the other end and the way the data goes; a dashed line
   (--write-back) is status written back to the system it was read from. */
.run-order__item::before,
.run-order__item::after {
  content: "";
  position: absolute;
  top: 50%;
}
.run-order__item::before {
  width: var(--run-gutter);
  border-top: 1px solid var(--wp--preset--color--graphic);
}
.run-order__item::after {
  border-block: 4px solid transparent;
  transform: translateY(calc(-50% + 0.5px));
}
.run-order__item--write-back::before {
  border-top-style: dashed;
}
.run-order__item--from-crm::before,
.run-order__item--to-crm::before {
  right: calc(100% + 1px);
}
.run-order__item--to-erp::before,
.run-order__item--from-erp::before {
  left: calc(100% + 1px);
}
.run-order__item--from-crm::after {
  right: calc(100% + 1px);
  border-left: 7px solid var(--wp--preset--color--graphic);
}
.run-order__item--to-crm::after {
  right: calc(100% + 1px + var(--run-gutter) - 7px);
  border-right: 7px solid var(--wp--preset--color--graphic);
}
.run-order__item--to-erp::after {
  left: calc(100% + 1px + var(--run-gutter) - 7px);
  border-left: 7px solid var(--wp--preset--color--graphic);
}
.run-order__item--from-erp::after {
  left: calc(100% + 1px);
  border-right: 7px solid var(--wp--preset--color--graphic);
}

/* The desktop window, from 960px of viewport. */
@media (min-width: 960px) {
  .portal-figure {
    --portal-shadow-far: 0 28px 72px rgba(27, 36, 44, 0.18);
  }
  .portal-window {
    width: var(--portal-desktop-width);
    zoom: min(1, tan(atan2(100cqw, var(--portal-desktop-width))));
  }
  .portal-window__bar {
    gap: 20px;
  }
  .portal-window__content {
    padding: 24px 28px 28px;
  }

  .run-order {
    --run-system: 132px;
    --run-gutter: 40px;

    padding: 16px;
  }
  .run-order::before {
    bottom: 24px;
  }
  .run-order__system {
    top: 16px;
    bottom: 16px;
    flex-direction: row;
    align-items: center;
    gap: 8px;
    padding: 12px;
    border-radius: 12px;
  }
  .run-order__system--crm {
    left: 16px;
  }
  .run-order__system--erp {
    right: 16px;
  }
  /* Centred in the post [Emilie 5 nov], the icon level with the name, not
     with the kicker above it: half the kicker and its gap further down. */
  .run-order__system svg {
    margin-top: 14px;
  }
  .run-order__system .run-order__name {
    display: block;
  }
  .run-order__lanes {
    padding-bottom: 12px;
  }
  /* 4px, not the post's 12px [Emilie 16 nov]: at 12 the name sat on the
     first step, with nothing but the 4px lane gap between them. */
  .run-order__platform {
    height: 44px;
    padding-top: 4px;
  }
  .run-order__item {
    gap: 10px;
    height: 28px;
    padding: 0 10px 0 4px;
  }
  .run-order__chevron {
    display: flex;
  }
}

/* The order record, the portal illustration 01 Records [Emilie 5 nov]:
   what happened to one order in the last run, a status line and a three
   step timeline. The heroes of the order to payment and reconciliation
   pages show it. The window,
   bar and title are the portal window above; this is what is inside it.
   Sizes from the handoff design_handoff_records, phone first like the
   window, desktop from 960.

   CYAN ON THE TIMELINE [beslut användare], from the handoff: the rail, the
   dots and the two check marks, where the design system keeps the signal
   colour for data in motion. The check inside a cyan circle is graphite
   deep, because white on cyan is 2.5:1. */
.portal-figure--records {
  --portal-desktop-width: 696px;
}
.order-record {
  margin-top: 16px;
  overflow: hidden;
  border: 1px solid var(--portal-line-box);
  border-radius: var(--radius-card);
}
.order-record__head {
  display: flex;
  flex-direction: column;
  gap: 8px;
  padding: 16px;
}
/* Paragraphs in the markup, so the page's paragraph spacing is undone. */
.order-record__meta,
.order-record__latest,
.order-record__day {
  margin: 0;
}
.order-record__meta {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 4px 6px;
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
}
/* Underlined like the link it is in the portal. Here it is a picture of
   one, inside role="img", and goes nowhere. */
.order-record__id {
  display: flex;
  align-items: center;
  gap: 4px;
  color: var(--wp--preset--color--text-strong);
}
.order-record__id span {
  text-decoration: underline;
  text-underline-offset: 2px;
}
.order-record__latest {
  display: flex;
  align-items: flex-start;
  gap: 10px;
  font-size: 14px;
  line-height: 1.45;
}
.order-record__check {
  flex: none;
  display: grid;
  place-items: center;
  width: 20px;
  height: 20px;
  border-radius: 50%;
  background: var(--signal-flow);
  color: var(--wp--preset--color--graphite-deep);
}
.order-record__latest .order-record__check {
  margin-top: 1px;
}
.order-record__check svg {
  stroke-width: 2.5;
}

.order-record__timeline {
  display: flex;
  flex-direction: column;
  gap: 8px;
  padding: 20px 16px 16px;
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.order-record__day {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
}
.order-record__steps {
  margin: 0;
  padding: 0;
  list-style: none;
}
.order-record__step {
  display: grid;
  grid-template-columns: 52px 20px minmax(0, 1fr);
  column-gap: 10px;
  min-height: 30px;
}
.order-record__step:last-child {
  min-height: 32px;
}
.order-record__time {
  display: flex;
  align-items: center;
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
}
.order-record__text {
  display: flex;
  align-items: center;
  padding: 6px 0;
  font-size: 12px;
  line-height: 1.4;
}
.order-record__step:last-child .order-record__text {
  font-size: 14px;
}
/* The rail runs from the first dot's centre to the last check's centre:
   down from the middle on the first row, the whole row on the next, down
   to the middle on the last. */
.order-record__node {
  position: relative;
  display: grid;
  place-items: center;
}
.order-record__node::before {
  content: "";
  position: absolute;
  top: 0;
  bottom: 0;
  left: calc(50% - 0.5px);
  width: 1px;
  background: var(--signal-flow);
}
.order-record__step:first-child .order-record__node::before {
  top: 50%;
}
.order-record__step:last-child .order-record__node::before {
  bottom: 50%;
}
.order-record__dot {
  position: relative;
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: var(--signal-flow);
}
.order-record__node .order-record__check {
  position: relative;
}

@media (min-width: 960px) {
  .order-record__head {
    padding: 16px 18px;
  }
  .order-record__meta {
    flex-wrap: nowrap;
    gap: 4px;
  }
  .order-record__latest {
    align-items: center;
    line-height: inherit;
  }
  .order-record__latest .order-record__check {
    margin-top: 0;
  }
  .order-record__timeline {
    padding: 20px 18px 16px;
  }
  .order-record__step {
    grid-template-columns: 64px 28px 1fr;
    column-gap: 12px;
    height: 30px;
    min-height: 0;
  }
  .order-record__step:last-child {
    height: 32px;
  }
  .order-record__text {
    padding: 0;
    line-height: inherit;
  }
}

/* Parallel run, the portal illustration 02 Parallell drift [Emilie 5 nov]:
   during an ERP change every transaction from the CRM goes to the current
   ERP and to the new one. The ERP change page's hero shows it. Sizes and
   paths from the handoff design_handoff_parallell_drift, phone first.

   A STAGE OF FIXED SIZE, 328 by 268 on the phone and 648 by 234 on the
   desktop, with the nodes placed on it and the arrows drawn in an SVG of
   the same size. The phone's coordinates are the handoff's own; the
   desktop is narrower than the handoff, see patterns/parallel-run.php. The two windows
   draw different paths, so there are two SVGs and one is shown. The whole
   window scales, so a fixed stage never meets a width it has to fit. */
.portal-figure--parallel {
  --portal-desktop-width: 727px;
}
.parallel-run {
  display: flex;
  justify-content: center;
  padding: 16px;
}
.parallel-run__stage {
  position: relative;
  flex: none;
  width: 328px;
  height: 268px;
}
.parallel-run__paths {
  position: absolute;
  inset: 0;
  overflow: visible;
}
.parallel-run__paths--desktop {
  display: none;
}
.parallel-run__paths path {
  fill: none;
  stroke: var(--wp--preset--color--graphic);
  stroke-width: 1.3;
}
.parallel-run__paths marker path {
  fill: var(--wp--preset--color--graphic);
  stroke: none;
}

.parallel-run__node {
  position: absolute;
  display: flex;
  align-items: center;
  border-radius: 10px;
}
/* A system: dark, an icon on a light tile and a name. No kicker
   [Emilie 6 nov]: the icon and the name say which system it is. */
.parallel-run__node--system {
  gap: 12px;
  width: 160px;
  min-height: 56px;
  padding: 0 14px;
  background: var(--wp--preset--color--graphite-deep);
  color: var(--wp--preset--color--text-on-dark);
}
.parallel-run__tile {
  flex: none;
  display: grid;
  place-items: center;
  width: 26px;
  height: 26px;
  border-radius: 6px;
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--graphite);
}
/* 14 and not the handoff's 13 [Emilie 6 nov], since the window is drawn
   smaller beside the words. Two lines where the node is too narrow. */
.parallel-run__name {
  font-size: 14px;
  font-weight: 500;
  line-height: 1.25;
}
/* The flow between them: light, a title and what it does. */
.parallel-run__node--flow {
  justify-content: space-between;
  left: 64px;
  top: 104px;
  width: 200px;
  height: 60px;
  padding: 0 14px;
  border: 1px solid var(--portal-line-box);
  background: var(--wp--preset--color--ground);
}
.parallel-run__text {
  display: flex;
  flex-direction: column;
  gap: 2px;
}
.parallel-run__title {
  font-size: 12px;
  line-height: 17px;
}
.parallel-run__sub {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  line-height: 15px;
}
.parallel-run__chevron {
  display: none;
  color: var(--wp--preset--color--text-body);
}

/* On the phone: the CRM on top, the flow under it, the two ERPs side by
   side at the bottom, narrower, so their padding and gap are smaller. */
.parallel-run__node--crm {
  left: 84px;
  top: 0;
  height: 56px;
}
.parallel-run__node--current,
.parallel-run__node--new {
  top: 212px;
  gap: 8px;
  padding: 0 10px;
}
.parallel-run__node--current {
  left: 0;
}
.parallel-run__node--new {
  left: 168px;
}
.parallel-run__node--current .parallel-run__name,
.parallel-run__node--new .parallel-run__name {
  font-size: 13px;
}

@media (min-width: 960px) {
  .parallel-run {
    align-items: center;
    height: 268px;
    padding: 0;
  }
  .parallel-run__stage {
    width: 648px;
    height: 234px;
  }
  .parallel-run__paths--mobile {
    display: none;
  }
  .parallel-run__paths--desktop {
    display: block;
  }
  .parallel-run__node--system {
    width: 140px;
    height: 70px;
    min-height: 0;
    gap: 10px;
    padding: 0 12px;
  }
  .parallel-run__node--crm {
    left: 0;
    top: 82px;
  }
  .parallel-run__node--current,
  .parallel-run__node--new {
    left: 508px;
  }
  .parallel-run__node--current {
    top: 24px;
  }
  .parallel-run__node--new {
    top: 140px;
  }
  .parallel-run__node--current .parallel-run__name,
  .parallel-run__node--new .parallel-run__name {
    font-size: 14px;
  }
  .parallel-run__node--flow {
    left: 204px;
    top: 87px;
    width: 240px;
    padding: 0 14px 0 16px;
  }
  .parallel-run__text {
    gap: 0;
  }
  .parallel-run__title {
    font-size: 14px;
    line-height: 20px;
  }
  .parallel-run__chevron {
    display: flex;
  }
}

/* The transaction log, the portal carousel's third window: the order
   record's status line and timeline (above), with a step that has not
   happened yet and a list of earlier transactions. From the handoff
   design_handoff_portalkarusell. .order-record__day is the small label
   over each part, here "Steg" and "Tidigare transaktioner".

   ONE WINDOW AT EVERY WIDTH, 696px. The handoff has no phone variant and
   scales the desktop one down, which is an open question there. */
.portal-figure--log {
  --portal-desktop-width: 696px;
}
.portal-figure--log .portal-window {
  width: var(--portal-desktop-width);
  zoom: min(1, tan(atan2(100cqw, var(--portal-desktop-width))));
}
.portal-figure--log .portal-window__content {
  padding: 24px 28px 28px;
}
/* The step still to come: hollow, on a grey rail. The rail into it turns
   grey halfway down the step before. The ring is the handoff's
   neutral-400, which the palette does not have. */
.order-record__step--pending .order-record__node::before {
  background: var(--portal-line-box);
}
.order-record__step:has(+ .order-record__step--pending) .order-record__node::before {
  background: linear-gradient(var(--signal-flow) 50%, var(--portal-line-box) 50%);
}
.order-record__step--pending .order-record__dot {
  width: 9px;
  height: 9px;
  border: 1.5px solid #6E7B86;
  background: var(--wp--preset--color--ground);
}
.order-record__step--pending:last-child {
  min-height: 30px;
}
.order-record__step--pending:last-child .order-record__text {
  color: var(--wp--preset--color--text-body);
  font-size: 12px;
}
.order-record__history {
  margin: 0;
  padding: 0;
  list-style: none;
}
.order-record__history-item {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  min-height: 30px;
  font-size: 12px;
}
@media (min-width: 960px) {
  .order-record__step--pending:last-child {
    height: 30px;
  }
}

/* Portal flows, the portal carousel's fourth window: the three flows
   between the CRM and the ERP, with the systems on either side. From the
   handoff design_handoff_portalkarusell, phone first like the window.

   A STAGE OF FIXED SIZE, 328 by 292 on the phone and 800 by 234 on the
   desktop, the handoff's own coordinates, with the arrows drawn in an SVG
   of the same size, as in the parallel run above.

   THE 12PX FLOOR HOLDS HERE. The handoff draws the kicker at 9px and the
   flow card's lines at 11px; CLAUDE.md grants an exception to the floor
   for .flow-stack only, and a role="img" does not make the text any
   easier to read. The phone's flow cards are 104px wide and 84px high, so
   the lines keep the handoff's 15px line height at 12px, and the sides
   give 2px each: at the handoff's 8px "Åt båda hållen" broke onto a
   second line and ran 8px out of the card. */
.portal-flows {
  display: flex;
  justify-content: center;
  padding: 16px;
}
.portal-flows__stage {
  position: relative;
  flex: none;
  width: 328px;
  height: 292px;
}
.portal-flows__paths {
  position: absolute;
  inset: 0;
  overflow: visible;
}
.portal-flows__paths--desktop {
  display: none;
}
.portal-flows__paths path {
  fill: none;
  stroke: var(--wp--preset--color--graphic);
  stroke-width: 1.3;
}
.portal-flows__paths marker path {
  fill: var(--wp--preset--color--graphic);
  stroke: none;
}
.portal-flows__node {
  position: absolute;
  display: flex;
  border-radius: 10px;
}
.portal-flows__node--system {
  align-items: center;
  gap: 12px;
  left: 84px;
  width: 160px;
  height: 56px;
  padding: 0 14px;
  background: var(--wp--preset--color--graphite-deep);
  color: var(--wp--preset--color--text-on-dark);
}
.portal-flows__node--crm {
  top: 0;
}
.portal-flows__node--erp {
  top: 236px;
}
.portal-flows__tile {
  flex: none;
  display: grid;
  place-items: center;
  width: 26px;
  height: 26px;
  border-radius: 6px;
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--graphite);
}
.portal-flows__system-text {
  display: flex;
  flex-direction: column;
  gap: 2px;
}
.portal-flows__kicker {
  color: var(--wp--preset--color--hairline);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
}
.portal-flows__name {
  font-size: 13px;
  font-weight: 500;
}
.portal-flows__node--flow {
  top: 104px;
  justify-content: space-between;
  width: 104px;
  height: 84px;
  padding: 8px 6px;
  border: 1px solid var(--portal-line-box);
  background: var(--wp--preset--color--ground);
}
.portal-flows__node--customers {
  left: 0;
}
.portal-flows__node--invoices {
  left: 112px;
}
.portal-flows__node--invoice-lines {
  left: 224px;
}
.portal-flows__text {
  display: flex;
  flex-direction: column;
  gap: 2px;
}
.portal-flows__title {
  font-size: 12px;
  line-height: 17px;
}
.portal-flows__sub {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  line-height: 15px;
}
.portal-flows__chevron {
  display: none;
  color: var(--wp--preset--color--text-body);
}

@media (min-width: 960px) {
  .portal-flows {
    align-items: center;
    height: 268px;
    padding: 0;
  }
  .portal-flows__stage {
    width: 800px;
    height: 234px;
  }
  .portal-flows__paths--mobile {
    display: none;
  }
  .portal-flows__paths--desktop {
    display: block;
  }
  .portal-flows__node--system {
    left: 0;
    top: 82px;
    width: 176px;
    height: 70px;
    padding: 0 16px;
  }
  .portal-flows__node--erp {
    left: 624px;
  }
  .portal-flows__node--flow {
    left: 264px;
    align-items: center;
    width: 272px;
    height: 60px;
    padding: 0 14px 0 16px;
  }
  .portal-flows__node--customers {
    top: 10px;
  }
  .portal-flows__node--invoices {
    top: 87px;
  }
  .portal-flows__node--invoice-lines {
    top: 164px;
  }
  .portal-flows__text {
    gap: 0;
  }
  .portal-flows__title {
    font-size: 14px;
    line-height: 20px;
  }
  .portal-flows__chevron {
    display: flex;
  }
}

/* ------------------------------------------------------------------
   Portal carousel [Emilie 16 nov]: the traceability page's second band.
   Five portal windows, the middle one at full size and its neighbours
   smaller and faded at the section's edges. From the handoff
   design_handoff_portalkarusell, which calls itself final; the geometry
   is in assets/js/portal-carousel.js, which also says what the band does
   without it.

   DEPARTURES FROM THE HANDOFF:
     - No #FFFFFF [Emilie 26 okt]. The buttons are the ground, their hover
       the light surface; the handoff's #F8F9FA hover would not show
       against #FAFAFA.
     - The section's padding is the handoff's, clamp(48px, 6vw, 96px),
       not --section-pad: the stage carries its own air above and below.
     - The run order's reading animation blurs the words in a step, not
       the step's box, and lifts the current step with the shadow alone,
       without the handoff's scale(1.04). The arrows between the steps are
       drawn by the step itself (::before and ::after), and the handoff
       keeps them sharp and still; a filter or a scale on the step would
       take them along.

   [beslut användare] The glass on the window bar, in the handoff's own
   strength here, since this band is light; the dark bands keep the thin
   glass under "Portal illustration".
   ------------------------------------------------------------------ */
.portal-carousel {
  --dur-slide: 450ms;

  overflow: hidden;
  padding-block: clamp(48px, 6vw, 96px);
}
.portal-carousel__head {
  display: flex;
  flex-wrap: wrap;
  align-items: flex-end;
  justify-content: space-between;
  gap: 24px;
}
/* The group's flow layout puts a block gap above each child. */
.portal-carousel__head > *,
.portal-carousel__stage > * {
  margin-block: 0;
}
.portal-carousel__head > .wp-block-heading {
  flex: 1 1 min(320px, 100%);
  min-width: 0;
}
.portal-carousel__controls {
  display: flex;
  align-items: center;
  gap: 16px;
}
.portal-carousel__controls[hidden] {
  display: none;
}
.portal-carousel__counter {
  color: var(--wp--preset--color--text-body);
  font-size: 13px;
  font-variant-numeric: tabular-nums;
}
.portal-carousel__arrows {
  display: inline-flex;
  overflow: hidden;
  border: 1px solid var(--wp--preset--color--graphite);
  border-radius: var(--radius-button);
}
.portal-carousel__arrow {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  padding: 0;
  border: 0;
  background: var(--wp--preset--color--ground);
  color: var(--wp--preset--color--text-strong);
  cursor: pointer;
  transition: background-color var(--dur-hover) var(--ease);
}
.portal-carousel__arrow + .portal-carousel__arrow {
  border-left: 1px solid var(--wp--preset--color--graphite);
}
.portal-carousel__arrow:hover:not([disabled]) {
  background: var(--wp--preset--color--surface);
}
/* The handoff's text-soft, 4.3:1 on the ground: a disabled control is
   exempt from contrast, and this still reads as an arrow. */
.portal-carousel__arrow[disabled] {
  color: #6E7B86;
  cursor: default;
}
/* Inside, because the pair's overflow: hidden would clip a ring outside. */
.portal-carousel__arrow:focus-visible {
  outline-offset: -4px;
}

.portal-carousel__stage {
  position: relative;
  margin-top: clamp(32px, 4vw, 56px);
  padding-inline: var(--gutter);
  touch-action: pan-y;
}
/* Without the script: the first window alone, centred. */
.portal-carousel:not(.is-enhanced) .portal-carousel__stage > .portal-figure:not(:first-child) {
  display: none;
}
.portal-carousel:not(.is-enhanced) .portal-window {
  margin-inline: auto;
}

/* With it: every window at its natural size, placed and scaled by the
   script. No container and no zoom, so offsetWidth reads the size the
   handoff draws from. Windows two or more steps away are invisible. */
.portal-carousel.is-enhanced .portal-carousel__stage {
  padding-inline: 0;
}
.portal-carousel.is-enhanced .portal-carousel__stage > .portal-figure {
  position: absolute;
  top: 0;
  left: 50%;
  z-index: 1;
  width: max-content;
  container-type: normal;
  opacity: 0;
  pointer-events: none;
  transform-origin: 50% 0;
}
.portal-carousel.is-enhanced .portal-carousel__stage > .portal-figure.is-neighbour {
  z-index: 2;
  opacity: 0.55;
  pointer-events: auto;
  cursor: pointer;
}
.portal-carousel.is-enhanced .portal-carousel__stage > .portal-figure.is-current {
  z-index: 3;
  opacity: 1;
  pointer-events: auto;
}
.portal-carousel.is-enhanced .portal-window {
  zoom: 1;
}
.portal-carousel.is-ready .portal-carousel__stage {
  transition: height var(--dur-slide) var(--ease);
}
.portal-carousel.is-ready .portal-carousel__stage > .portal-figure {
  transition:
    transform var(--dur-slide) var(--ease),
    opacity var(--dur-slide) var(--ease);
}

/* [beslut användare] The handoff's glass and window lights, for a light
   band. */
.portal-carousel .portal-window {
  background: linear-gradient(180deg, rgba(255, 255, 255, 0.8), rgba(255, 255, 255, 0.62));
}
.portal-carousel .portal-window__bar {
  box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.9);
}
.portal-carousel .portal-window__lights i {
  background: var(--wp--preset--color--graphite);
}
.portal-carousel .portal-window__lights i:nth-child(2) {
  background: #3F5563;
}
.portal-carousel .portal-window__lights i:nth-child(3) {
  background: var(--wp--preset--color--text-body);
}

/* The caption under the middle window: its name, and the word
   Illustration, which the design system asks for on data that looks real.
   The script sets its top and width; its left edge follows the window's.
   The five names share one grid cell and fade between each other. */
.portal-carousel__caption {
  position: absolute;
  left: 50%;
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  justify-content: space-between;
  gap: 4px 16px;
  transform: translateX(-50%);
}
.portal-carousel__caption[hidden] {
  display: none;
}
.portal-carousel.is-ready .portal-carousel__caption {
  transition:
    top var(--dur-slide) var(--ease),
    width var(--dur-slide) var(--ease);
}
.portal-carousel__names {
  display: grid;
}
.portal-carousel__name {
  grid-area: 1 / 1;
  color: var(--wp--preset--color--text-strong);
  font-size: 15px;
  font-weight: 500;
  line-height: 1.4;
  opacity: 0;
  transition: opacity var(--dur-surface) var(--ease);
}
.portal-carousel__name.is-current {
  opacity: 1;
}
.portal-carousel__tag {
  color: var(--wp--preset--color--text-body);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
}

/* The run order, read one step at a time (assets/js/portal-carousel.js):
   the words in a step ahead of the reader are blurred, the current step
   is lifted. With reduced motion the script does not run it and nothing
   is blurred. */
.portal-carousel.is-enhanced .run-order__item {
  transition: box-shadow 420ms ease;
}
.portal-carousel.is-enhanced .run-order__item > * {
  transition: filter 520ms ease;
}
@media (prefers-reduced-motion: no-preference) {
  .portal-carousel.is-enhanced .run-order__item:not(.is-read) > * {
    filter: blur(3px);
  }
}
.portal-carousel.is-enhanced .run-order__item.is-reading {
  box-shadow: 0 6px 18px rgba(27, 36, 44, 0.16);
}

/* ------------------------------------------------------------------
   Partner page.

   Seven bands, and nearly all of them are parts the theme already has:
   the feature columns and the system grid from the process and contact
   pages, the form slot from the contact page.

   What is new is the numbered step list beside the technology track.
   ------------------------------------------------------------------ */

/* The hero carries the flow figure and clips it. */
.section--partner-hero {
  position: relative;
  overflow: hidden;
}
.section--partner-hero > .container {
  position: relative;
  z-index: 1;
}
/* Matted on white, which is this band's own ground.

   NOT flow-dark.webp. A darker figure was asked for [Emilie 6 okt] and
   that file is not the way to it: all three flow files are fully opaque
   with their matte baked in, measured, flow.webp on white 255, flow-dark
   on rgb(44, 53, 69) and flow-deep on rgb(27, 35, 42). On this white band
   either dark file paints a graphite rectangle. The dial that darkens the
   ribbon here is the opacity.

   0.9, WHICH IS THE DESIGN'S OWN NUMBER. No contrast reserve is needed
   against words reaching the figure, because they do not: measured, the
   ink's leftmost point stands 213px
   from the end of the longest line at 1440, 189px at 1366 and 91px at
   1060, the last width before the figure is dropped altogether.

   WHAT THAT COSTS, measured on the part of the file this band draws.
   Its deepest pixel there is rgb(3, 116, 151), on row 1317, which at 0.9
   lands on rgb(28, 130, 161). Strong ink would read 2.84:1 against that
   and body ink 1.30:1, so neither may cross it. THE FIGURE MOVES BEFORE
   THIS NUMBER DOES if a line ever grows that far: 0.55 is where the
   strong ink clears 4.5:1 again. */
.section--partner-hero::before {
  content: "";
  position: absolute;
  z-index: 0;
  /* THE FIGURE BEGINS INSIDE THE BAND. A negative top clips its start, so
     the ribbon enters the page already in progress, sawn off by the top
     edge.

     0 and not a positive number, because the file opens with empty rows:
     measured on flow.webp, the first ink is at row 120 of 4379, which is
     47px down at this size. The figure begins on its own just inside the
     band. Its foot is still cut by the band below, which is the
     composition the design asks for. */
  top: 0;
  /* IN FROM THE EDGE, NOT AGAINST IT. Mirrored, the ink sits at the right
     of its own box instead of the left, and the tilt throws that end a
     further 150px out: with a small inset the figure leaves the band
     and a sliver is all that shows. */
  right: calc(var(--outside-container) + clamp(140px, 23vw, 360px));
  /* NARROW, which is what makes the ribbon read as dark rather than as a
     wash. The file is pale at its top and deepens as it falls: the
     darkest pixel in its first thousand rows is rgb(20, 129, 161), by row
     1317 it is rgb(3, 116, 151). Width sets height through the aspect
     ratio, so a narrower figure is a shorter one and more of its length
     fits the 572px band: 33 per cent of the file at 1440, which brings
     that deeper stretch inside the band. Thinner, and the design's own
     stroke is thin. */
  width: clamp(110px, 12vw, 180px);
  aspect-ratio: 440 / 4379;
  background: url("assets/media/flow.webp?v=2") center top / 100% 100% no-repeat;
  opacity: 0.9;
  /* MIRRORED, so the ribbon leans the way the design asks [Emilie 6 okt].
     The file's own curve starts at its left edge and sweeps right as it
     falls, measured: the ink's centre of mass runs x 18, 72, 121, 150
     down the rows this band draws. The band wants the opposite, a top at
     the right that bends left and straightens. scaleX is the whole of it;
     the figure is abstract and has no reading direction to protect.

     Mirrored first, then tilted, so the 8 degrees still carry the top to
     the right rather than being flipped with it. */
  transform: rotate(8deg) scaleX(-1);
  pointer-events: none;
}
@media (max-width: 1020px) {
  .section--partner-hero::before {
    display: none;
  }
}

/* The steps beside the technology track: a title and a short text,
   divided by hairlines.

   NO NUMBERS [Emilie 12 okt], and no column for them. The list is an ol,
   so the order is still said to a screen reader. */
.step-rows {
  margin: 0;
  padding: 0;
  list-style: none;
}
.step-row {
  padding-block: var(--wp--preset--spacing--50);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
/* No rule between the label and the first step [Emilie 20 okt]: the
   hairlines divide steps, they do not underline the label. Without the
   rule the padding has nothing to keep apart, so the label's own margin
   is the whole gap. */
.step-row:first-child {
  padding-top: 0;
  border-top: 0;
}
.step-row > * {
  margin-block: 0;
}
.step-row__title {
  margin: 0;
  /* rubrik-1, NOT rubrik-2: at 18px the heading would be smaller than the
     19px body text beside it. See .trust__title. */
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.3;
}
.step-row__text {
  max-width: 48ch;
  margin: var(--wp--preset--spacing--20) 0 0;
  font-size: 15px;
  line-height: 1.7;
  color: var(--wp--preset--color--text-body);
  text-wrap: pretty;
}
/* The label over the list. No rule under it, see .step-row:first-child. */
.step-rows__label {
  margin: 0 0 var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}

/* ------------------------------------------------------------------
   Policy page.

   Two bands: a heading with the flow figure, and the text in a column
   with a table of contents beside it.

   THE CONTENTS LIST IS BUILT FROM THE TEXT, in PHP, out of whatever
   second level headings the page carries. It is anchor links and
   nothing else: no script, no active state that follows the scroll. The
   design highlights the section you are in, which needs a scroll
   listener; anchor links work without one and degrade to nothing when
   the text has no headings, which is what the published policy looks
   like today.
   ------------------------------------------------------------------ */
/* THE LABEL SITS NEAR THE TOP OF THE PAGE, not a band's distance down it
   [Emilie 6 okt]. Every other hero opens with a display heading, which
   fills the space the rhythm gives it; this one opens with a one line
   label and a rule, and at the full 112px the page read as empty above
   its own name.

   Half the rhythm, written as half of it rather than as 56px, so the two
   stay related if the band spacing is ever retuned. The foot keeps its
   own distance: what changed is where the page starts, not how it ends.

   Both legal pages are this section; see inc/legal.php. */
.section--policy-hero {
  position: relative;
  padding-top: calc(var(--section-pad) / 2);
  padding-bottom: var(--stack-lg);
}

/* THE RIBBON RUNS PAST THE HERO, 2 okt. Drawn on the hero section, which
   clips its own overflow, the figure would stop dead on the hero's bottom
   edge: the file is 440 by 4379, about 1990px tall at the width it is
   given, and roughly a quarter of it would show.

   Drawn on the page instead. The main element is the only box that
   contains both bands, so it is what the figure is positioned against
   and what clips it at the foot of the page. The template says which
   pages are this page; see inc/legal.php. */
.site-main--policy {
  position: relative;
  overflow: hidden;
}
/* THE WHOLE FIGURE, NOT A SLICE OF IT.

   top: 0, so the loop starts on the page and the first curve is seen.

   THE HEIGHT IS THE BOX, AND THE WIDTH FOLLOWS IT. The file is 440 by
   4379, which is 1990px tall at the 200px it is given, and the cookie page
   is 809px tall in total. Sized by width it is cut off at the foot of that
   page. Sized by height, capped at the page, the width comes out of the
   aspect ratio and the whole figure fits whatever the page is: 200 by 1990
   on the policy, 81 by 809 on the cookie page.

   NO TILT. A tall box inside one that clips its overflow cannot be
   rotated and stay whole: at 1990px tall, eight degrees swings the corners
   138px sideways, and there are 57px of page beside it at 1440. The
   figure has its own curve.

   THE FILE ITSELF IS CROPPED AT THE FOOT, and no CSS undoes that. All
   three flow files are 440 by 4379 and the ribbon runs off their last
   pixel row: counted on row 4378, flow.webp has 87 strokes of ink
   across it, flow-dark 62, flow-deep 91. Their top rows are empty, so
   the figure begins on its own and only ends by being cut.

   So the foot is faded out rather than shown. A figure that dissolves
   reads as going on past the page; one that stops on a straight edge
   reads as broken. The same answer, and the same mask, as the partner
   band's two ends. A file that ends by itself would be better and is
   a question for the design source, not for this file. */
.site-main--policy::before {
  content: "";
  position: absolute;
  z-index: 0;
  top: 0;
  right: calc(var(--outside-container) + clamp(-40px, 4vw, 120px));
  height: min(calc(clamp(120px, 14vw, 200px) * 4379 / 440), 100%);
  aspect-ratio: 440 / 4379;
  background: url("assets/media/flow.webp?v=2") center / 100% 100% no-repeat;
  opacity: 0.55;
  /* The last 28 per cent dissolves. See the note above: the file is cut. */
  -webkit-mask-image: linear-gradient(to bottom, #000 72%, transparent);
  mask-image: linear-gradient(to bottom, #000 72%, transparent);
  pointer-events: none;
}

/* Both bands stand above it, not only the hero. A figure behind the
   reading column is a figure over the words without this. */
.site-main--policy > article > .section {
  position: relative;
  z-index: 1;
}
.section--policy-hero > .container {
  position: relative;
  z-index: 1;
}
@media (max-width: 1020px) {
  .site-main--policy::before {
    display: none;
  }
}

/* The two lines under the lead: when it was last changed and who is
   answerable for it. */
.policy-meta {
  display: flex;
  flex-wrap: wrap;
  gap: var(--wp--preset--spacing--20) var(--wp--preset--spacing--70);
  margin: clamp(32px, 4vw, 48px) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.6;
  color: var(--wp--preset--color--text-body);
}
.policy-meta > span {
  margin: 0;
}

/* THE BAND ADDS NOTHING ABOVE THE RULE [Emilie 6 okt]. The hairline is
   drawn by .policy-layout, which sits inside this section, so the band's
   own 112px pushed the rule down and the gap above it was two paddings
   stacked: 86 from the hero's foot and 112 from here, 199px between the
   meta line and a rule that has 72px under it.

   One owner per side instead. Above the rule is the hero's foot, below it
   is the layout's padding, and this band contributes nothing to either.
   Its foot is untouched: that is the distance to the footer. */
.section--policy-body {
  padding-top: 0;
}

/* The text and its contents list. The article takes the remaining room
   and stops at a reading measure; the list keeps its own column and
   follows the page down while there is a column for it to follow. */
.policy-layout {
  display: flex;
  flex-wrap: wrap;
  gap: clamp(40px, 6vw, 96px);
  align-items: flex-start;
  padding-top: clamp(40px, 5vw, 72px);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.policy-layout > * {
  margin-block: 0;
}
.policy-toc {
  flex: 1 1 240px;
  max-width: 300px;
  min-width: 0;
}
.policy-body {
  flex: 999 1 480px;
  max-width: 76ch;
  min-width: 0;
}
.policy-body > :first-child {
  margin-top: 0;
}
@media (min-width: 1021px) {
  .policy-toc__inner {
    position: sticky;
    top: calc(var(--header-height) + var(--wp--preset--spacing--50));
  }
}
.policy-toc__label {
  margin: 0 0 var(--wp--preset--spacing--40);
  font-size: var(--wp--preset--font-size--mikro);
  font-weight: 600;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--wp--preset--color--text-body);
}
.policy-toc__list {
  margin: 0;
  padding: 0;
  list-style: none;
}
.policy-toc__link {
  display: flex;
  gap: var(--wp--preset--spacing--30);
  padding: var(--wp--preset--spacing--30) 0 var(--wp--preset--spacing--30) var(--wp--preset--spacing--40);
  border-left: 1px solid var(--wp--preset--color--hairline);
  font-size: var(--wp--preset--font-size--brod-liten);
  line-height: 1.45;
  color: var(--wp--preset--color--text-strong);
  text-decoration: none;
}
.policy-toc__link:hover,
.policy-toc__link:focus-visible {
  border-left-color: var(--wp--preset--color--graphite);
  text-decoration: underline;
  text-underline-offset: 4px;
}
.policy-toc__n {
  flex: none;
  min-width: 22px;
  color: var(--wp--preset--color--text-body);
  font-variant-numeric: tabular-nums;
}

/* ------------------------------------------------------------------
   Platform page.

   Seven bands, and the theme already owns nearly all of them: the
   ownership panels and the trust grid from the front page, the feature
   columns from the process page, the flow diagram from the ERP migration
   page, the partner band, the closing band with its ribbon.

   New here: the hero that sets its words beside the figure rather than
   under it, the wide fan diagram, and the placeholder for a customer
   case.
   ------------------------------------------------------------------ */
/* NO HEIGHT OF ITS OWN [Emilie 6 okt]. Only the front page opens on a band
   sized to the window; every other page's opening band is as tall as what
   is in it.

   Its content is 348px, the same as the partner page's to the pixel, so
   with no floor the band is 112 + 348 + 112 and the two pages agree
   without either naming a number. */
.section--platform-hero {
  position: relative;
  overflow: hidden;
}
.section--platform-hero > .container {
  position: relative;
  z-index: 1;
}
/* The words stop before the figure rather than running under it, so the
   two never meet and the figure needs no opacity to stay out of the way.
   Below the width where the figure is hidden, the column is the whole
   container again. */
.platform-hero__col {
  max-width: min(760px, calc(100% - clamp(130px, 24vw, 400px)));
}
/* The heading's bold half on a line of its own, where a br used to put it
   [16 nov]. A br is no space in the text, so the heading read
   "plattformmed" to search results and screen readers. */
.section--platform-hero .display--page b {
  display: block;
}
/* THE RIBBON BELONGS TO THE PAGE, NOT TO THE HERO, 6 okt. On the hero it
   would be cut by the band, which leaves a short slab with two sawn ends.
   The contact page hangs its figure on the page instead and lets the next
   opaque band end it; this does the same.

   WHAT ENDS IT IS THE FIRST BAND WITH A BACKGROUND. The figure is 440 by
   4379, so at 300px wide it runs about 2990px, and the surface band on
   this page starts at 1951. The sections are lifted above it so an opaque
   one covers it and a transparent one lets it through. No height to keep
   in step with the page: the figure is simply longer than the run.

   The look is the contact page's, to the declaration: matted on white,
   cover, six degrees, and on the container's outer edge. */
.site-main--platform {
  position: relative;
  overflow: hidden;
}
.site-main--platform > .section {
  position: relative;
  z-index: 1;
}
.site-main--platform::before {
  content: "";
  position: absolute;
  z-index: 0;
  top: -80px;
  right: calc(var(--outside-container) + clamp(-64px, -1vw, 0px));
  width: clamp(200px, 17vw, 300px);
  aspect-ratio: 440 / 4379;
  background: url("assets/media/flow.webp?v=2") center 10% / cover no-repeat;
  opacity: 0.55;
  transform: rotate(6deg);
  pointer-events: none;
}
/* AND NOTHING AFTER IT TAKES THE RIBBON BACK [Emilie 6 nov]. The figure is
   longer than the run, so at 300px wide its tail outlasted the surface band
   and came through the transparent contact band below, beside that band's
   own ribbon. Every band after the first opaque one is painted the page's
   ground: no visible change, and the ribbon ends where the opaque band cut
   it, at every width. */
.site-main--platform > :is(.section--surface, .section--dark) ~ .section {
  background-color: var(--wp--preset--color--ground);
}
@media (max-width: 1020px) {
  .site-main--platform::before {
    display: none;
  }
  .platform-hero__col {
    max-width: none;
  }
}

/* The wide diagram: four systems in, four out, everything through one
   point. Wider than the ERP migration page's, so it gets its own box
   rather than a modifier on that one.

   A dash runs along all eight paths and the hub pulses with it, through
   the flow diagram's rules. */
.flow-fan {
  display: block;
  width: 100%;
  max-width: 1100px;
  height: auto;
  margin-inline: auto;
  margin-top: clamp(40px, 5vw, 72px);
}
/* Below 720 the fan is replaced, not dropped, by .flow-stack after it: the
   same drawing turned on its end, sources across the top, the hub in the
   middle, targets across the bottom, each node with its icon.

   BACK TO THE STACK [Emilie 22 okt]. .flow-tall replaced it for a morning
   and is reverted for this diagram and for the AI page's; the other
   pattern diagrams keep .flow-tall. The stack is a viewBox, so its labels
   shrink with a narrow window and do not grow with text zoom. That is the
   known cost of keeping the wide drawing's look standing up. */
.flow-stack {
  display: none;
  width: 100%;
  max-width: 320px;
  height: auto;
  margin-inline: auto;
}
/* The AI page's stack: the wide drawing turned a quarter, with its three
   dashed callouts beside the axis. 389 units across at full label size,
   the same margin left of the first label as right of the widest
   callout, so it may be as wide as its viewBox before the text shrinks. */
.flow-stack--callouts {
  max-width: 389px;
}
/* Four labels standing side by side in 320 units get eighty each, and the
   longest of them is twelve characters. 11px is what fits; the fan's 14
   does not. */
.flow-diagram__label--small {
  font-size: 11px;
}

/* ------------------------------------------------------------------
   The flow on its end [Emilie 22 okt].

   The diagrams written as core/html in the page patterns (order to
   payment, ERP migration) are one wide SVG each. Below 720px its
   viewBox shrinks the labels to five to seven pixels, so the same idea as
   the fan and .flow-stack above applies: the wide drawing is replaced, not
   dropped, by one that says the same thing standing up. The source on top,
   Syncify under it, the targets under that.

   HTML AND NOT A SECOND SVG. .flow-stack is still a viewBox, and a viewBox
   scales its text with the box: at 320px it would land below body size
   again, and it does not grow with text zoom or take text spacing (WCAG
   1.4.4, 1.4.12). Here every word is HTML text at body size, and only the
   lines and circles are drawn, by borders.

   ONE RAIL. Every node is centred on the same vertical line, so the
   column of text beside it starts at one left edge and keeps the full
   width at 320px. The second target is reached by a bypass: a soft curve
   out of the hub, past the first target, and back into the second, so it
   cannot be read as fed by the first. Written for two targets, which is
   what the pattern figures have; a target between the first and the last
   peels off the bypass on a curve of its own, for a figure with more.
   The mechanism diagram and the AI page's figure use .flow-stack instead
   [Emilie 22 okt], above.

   SOURCES, when there are several, are the same picture upside down: the
   last stands on the rail over the hub, the others join a bypass that
   curves into the rail under it, so none reads as passing through the
   next.

   The wide SVG hides where a .flow-tall follows it, which is the condition
   and not a class on each SVG. One of the two is always display: none, so
   the figure is read once.

   MOTION FOLLOWS THE WIDE DRAWING. A dash runs down the source line and
   the ring pulses only where the SVG beside it has flow paths, so
   /erp-byte/ stays still here as well [Emilie 9 okt]. The outbound lines
   carry no dash: the bypass is a curve made of borders, and a dash cannot
   follow it. Same ink, keyframes and resting state as .flow-diagram__flow.
   ------------------------------------------------------------------ */
.flow-tall {
  /* The geometry, in the ratio the fan draws: node and hub as in the
     stacked mechanism diagram, the stroke the SVGs' 1.5. */
  --flow-tall-node: 32px;
  --flow-tall-hub: 56px;
  --flow-tall-line: 1.5px;
  --flow-tall-gap: var(--wp--preset--spacing--30);
  --flow-tall-step: var(--wp--preset--spacing--50);
  --flow-tall-mid: calc(var(--flow-tall-hub) / 2);
  --flow-tall-text: calc(var(--flow-tall-hub) + var(--flow-tall-gap));

  display: none;
  margin: 0;
  color: var(--panel-ink, var(--wp--preset--color--text-strong));
  font-size: var(--wp--preset--font-size--brod);
  overflow-wrap: break-word;
}
.flow-tall > * {
  margin: 0;
}
/* A system: an empty circle on the rail, its name beside it. min-height
   and not height, so a name that wraps under zoom pushes the rail down
   instead of running over it. */
.flow-tall__node {
  position: relative;
  display: flex;
  align-items: center;
  min-height: var(--flow-tall-node);
  padding-left: var(--flow-tall-text);
  /* The name is an anonymous flex item, which min-width cannot reach, so
     break-word alone let "Rapportering" run out of the column at 320 with
     text at 200 per cent. anywhere lets it shrink; at 100 per cent no
     name is near the edge and nothing breaks. */
  overflow-wrap: anywhere;
}
.flow-tall__node::before {
  content: "";
  position: absolute;
  top: 0;
  left: calc(var(--flow-tall-mid) - var(--flow-tall-node) / 2);
  box-sizing: border-box;
  width: var(--flow-tall-node);
  height: var(--flow-tall-node);
  border: var(--flow-tall-line) solid var(--wp--preset--color--hairline);
  border-radius: 50%;
  background: var(--panel-bg, var(--wp--preset--color--ground));
}
/* What travels along a line, and the requirement callouts on /artificial-
   intelligence/. Body size like the names; the quiet colour is what says
   they annotate. */
.flow-tall__note {
  display: block;
  padding-left: var(--flow-tall-text);
  color: var(--panel-quiet, var(--wp--preset--color--text-body));
}
/* The line from the source down to the hub, with the notes beside it. */
.flow-tall__link {
  position: relative;
  margin-left: calc(var(--flow-tall-mid) - var(--flow-tall-line) / 2);
  padding-block: var(--flow-tall-step);
  border-left: var(--flow-tall-line) solid var(--wp--preset--color--hairline);
}
/* Back out of the line's own offset, so the notes start on the same left
   edge as the names. */
.flow-tall__link > * {
  margin-left: calc(-1 * (var(--flow-tall-mid) + var(--flow-tall-line) / 2));
}
/* The dash: a short bar in a strip over the line, moved by its background
   position so the strip's own box clips it at both ends. At rest it sits
   above the strip, which is drawn as nothing. */
.flow-tall__link::after {
  content: "";
  position: absolute;
  top: 0;
  bottom: 0;
  left: calc(var(--flow-tall-line) / -2 - 1.25px);
  width: 2.5px;
  background: linear-gradient(var(--status-deviation-ink), var(--status-deviation-ink)) 0 -16px / 100% 16px no-repeat;
}
/* Syncify: the graphite circle with the mark, as in the wide drawing, and
   the ring around it. A callout can stand beside it. */
.flow-tall__hub {
  position: relative;
  display: flex;
  align-items: center;
  gap: var(--flow-tall-gap);
}
/* The rail runs on behind the hub. A callout that wraps to more lines
   than the hub is tall makes the row taller than the circle, and the
   circle is centred in it; without this the line would stop short of it. */
.flow-tall__hub::before {
  content: "";
  position: absolute;
  top: 0;
  bottom: 0;
  left: calc(var(--flow-tall-mid) - var(--flow-tall-line) / 2);
  border-left: var(--flow-tall-line) solid var(--wp--preset--color--hairline);
}
.flow-tall__core {
  position: relative;
  flex: none;
  display: grid;
  place-items: center;
  width: var(--flow-tall-hub);
  height: var(--flow-tall-hub);
  border-radius: 50%;
  background: var(--wp--preset--color--graphite);
}
.flow-tall__core img {
  display: block;
  width: 57%;
  height: auto;
}
.flow-tall__core::after {
  content: "";
  position: absolute;
  inset: calc(-1 * var(--wp--preset--spacing--20));
  border: var(--flow-tall-line) solid var(--wp--preset--color--hairline);
  border-radius: 50%;
}
/* The targets. The first hangs straight under the hub on the rail. */
.flow-tall__branches {
  margin: 0;
  padding: 0;
  list-style: none;
}
.flow-tall__branch {
  position: relative;
  padding-top: var(--flow-tall-step);
}
.flow-tall__branch:first-child::before {
  content: "";
  position: absolute;
  top: 0;
  left: calc(var(--flow-tall-mid) - var(--flow-tall-line) / 2);
  height: var(--flow-tall-step);
  border-left: var(--flow-tall-line) solid var(--wp--preset--color--hairline);
}
/* The bypass, in two halves that meet where the branches do, so each half
   is measured on its own item and a name that wraps cannot break it. The
   first curves out of the hub and runs down past the first target; the
   second runs on and curves into the middle of the last node, which is
   painted after it and covers the end. Out beside the node circles and
   short of the text column. */
.flow-tall__branch::after {
  content: "";
  position: absolute;
  left: calc(var(--flow-tall-mid) - var(--flow-tall-line) / 2);
  width: calc(var(--flow-tall-node) / 2 + var(--flow-tall-gap));
  border: 0 solid var(--wp--preset--color--hairline);
  border-right-width: var(--flow-tall-line);
}
.flow-tall__branch:first-child::after {
  top: 0;
  bottom: 0;
  border-top-width: var(--flow-tall-line);
  border-top-right-radius: var(--flow-tall-gap);
}
.flow-tall__branch:last-child::after {
  top: 0;
  height: calc(var(--flow-tall-step) + var(--flow-tall-node) / 2);
  border-bottom-width: var(--flow-tall-line);
  border-bottom-right-radius: var(--flow-tall-gap);
}
/* A target between the first and the last: the bypass runs straight
   past it, and a curve of the same radius leaves it into the node's
   middle. Only lists of three or more have one. */
.flow-tall__branch:not(:first-child, :last-child)::after {
  top: 0;
  bottom: 0;
}
.flow-tall__branch:not(:first-child, :last-child)::before {
  content: "";
  position: absolute;
  top: calc(var(--flow-tall-step) + var(--flow-tall-node) / 2 - var(--flow-tall-gap));
  left: calc(var(--flow-tall-mid) - var(--flow-tall-line) / 2);
  width: calc(var(--flow-tall-node) / 2 + var(--flow-tall-gap));
  height: var(--flow-tall-gap);
  border: 0 solid var(--wp--preset--color--hairline);
  border-right-width: var(--flow-tall-line);
  border-bottom-width: var(--flow-tall-line);
  border-bottom-right-radius: var(--flow-tall-gap);
}
.flow-tall__branch > .flow-tall__node {
  z-index: 1;
}

:where(.flow-diagram:has(.flow-diagram__flow) ~ .flow-tall) .flow-tall__link::after {
  animation: syncify-flow-tall-dash 3.2s linear infinite backwards;
}
:where(.flow-diagram:has(.flow-diagram__flow) ~ .flow-tall) .flow-tall__core::after {
  animation: syncify-flow-hub 3.2s var(--ease, ease-in-out) infinite;
}
@keyframes syncify-flow-tall-dash {
  0%   { background-position: 0 -16px; }
  80%  { background-position: 0 calc(100% + 16px); }
  100% { background-position: 0 calc(100% + 16px); }
}
@media (prefers-reduced-motion: reduce) {
  .flow-tall__link::after,
  .flow-tall__core::after {
    animation: none;
  }
}

/* UNDER 720, and 720 itself keeps the wide drawing [Emilie 22 okt]: the
   decision reads "under 720 px", "720 and wider unchanged". The fan used
   to switch at 720 inclusive, to .flow-stack; it switches here now with
   the rest, so the whole site has one breakpoint for standing up. The
   transaction log and the ERP table below use the same one. */
@media (max-width: 719.98px) {
  .flow-diagram:has(~ .flow-tall),
  .flow-diagram:has(~ .flow-stack) {
    display: none;
  }
  .flow-tall,
  .flow-stack {
    display: block;
  }
}

/* The customer case, before there is one. A square for the portrait or
   the mark, and the quote beside it.

   EVERYTHING IN IT IS A PLACEHOLDER, in the design as well as here: no
   customer name, no portrait and no quote until the control matrix for
   partner and customer names clears. Guardrail 7, the same as the
   partner band before it had its approval box. */
.case-row {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 280px), 1fr));
  gap: clamp(28px, 4vw, 64px);
  align-items: start;
  margin-top: clamp(32px, 4vw, 56px);
}
.case-row > * {
  margin-block: 0;
}
.case-row__body {
  grid-column: span 2;
  min-width: 0;
}
@media (max-width: 860px) {
  .case-row__body {
    grid-column: auto;
  }
}
.case-row__quote {
  max-width: 32ch;
  margin: 0;
  font-size: clamp(22px, 2.2vw, 32px);
  font-weight: 300;
  line-height: 1.35;
  letter-spacing: -0.01em;
  text-wrap: pretty;
}
.case-row__who {
  margin: var(--wp--preset--spacing--40) 0 0;
  font-size: 15px;
  font-weight: 500;
}
.case-row__org {
  margin: var(--wp--preset--spacing--10) 0 0;
  font-size: 14px;
  color: var(--wp--preset--color--text-body);
}
/* The customer's logotype over the name, on the partner category pages
   (patterns/rows-quote-form.php). Empty there until a customer is cleared,
   and an empty image block renders nothing, so this only draws once a file
   is chosen. Held to a logotype's height so a large upload does not become
   a picture. */
.case-row__mark {
  margin: 0;
}
.case-row__mark img {
  width: auto;
  max-width: 160px;
  height: auto;
  max-height: 48px;
}

/* ------------------------------------------------------------------
   Article.

   The one page type whose whole job is to be read. A heading, the date,
   a picture and the text, and almost nothing is added here because the
   theme already owns the parts: .site-main gives the 1440 region and
   the gutters, the rule under "The content column" caps the article's
   children at 1080, and the measure rule caps a paragraph at 68ch.

   NO HEADING SIZES OF ITS OWN. The type scale in theme.json already
   decides what an h2 in running text looks like, and the policy page,
   which is the theme's other long text out of the_content(), lives with
   exactly those sizes. A second opinion here would make two long texts
   on the same site read as two different sites.
   ------------------------------------------------------------------ */
/* ONE CENTRED COLUMN, TEXT LEFT ALIGNED [Emilie 13 nov]. The article used
   to sit on the 1080 column's left edge like every other page. Now the
   heading, the picture and the body share one column at the text measure,
   centred in the window, so they keep a common left edge; centring each
   child on its own would give the 1080 head and the 683 body two different
   ones. The measure is read here, on the 16px article, where 68ch is 683px.

   This overrides the note on the content column rule that the article is
   a wrapper and never constrained: an article has no bands to break out. */
/* z-index 0 makes the article its own stacking context, so the ribbon's -1
   lands behind the text but in front of the body's ground, which it did
   not without it. */
.site-main--article > article {
  position: relative;
  z-index: 0;
  width: 100%;
  max-width: var(--text-measure);
  margin-inline: auto;
}

/* THE RIBBON, AS ON THE CONTACT PAGE [Emilie 13 nov]: the same file at the
   same opacity, in the margin right of the column and never over the text,
   so none of the contrast measurements under "WHICH COLOURWAY" arise. Teal,
   flow.webp, not the cyan file: cyan is the signal colour and is not worn
   by decoration.

   From the article's top, the figure's lead-in first, and cut by the
   article's lower edge: at 160px the figure is about 1590px tall.

   Only where the margin holds it. The width is what lies between the
   column plus a gap and the window less the gutter, capped at 160px, as on
   the contact page. Below 1100 that falls under about 120px and the figure
   reads as a thread, so it goes. */
@media (min-width: 1100px) {
  .site-main--article > article::before {
    content: "";
    position: absolute;
    z-index: -1;
    top: 0;
    left: calc(100% + var(--wp--preset--spacing--60));
    width: min(160px, calc((100vw - 100%) / 2 - var(--wp--preset--spacing--60) - var(--gutter)));
    height: 100%;
    background: url("assets/media/flow.webp?v=2") center top / 100% auto no-repeat;
    opacity: 0.55;
    pointer-events: none;
  }
}

.article__title {
  margin: 0;
}
/* Published, and updated when it is a different day. Two time elements
   on one line, far enough apart to read as two statements. */
.article__meta {
  display: flex;
  flex-wrap: wrap;
  gap: var(--wp--preset--spacing--20) var(--wp--preset--spacing--60);
  margin: var(--wp--preset--spacing--50) 0 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--wp--preset--color--text-body);
}

/* The picture. figure carries a 40px inline margin from the user agent
   that nothing else in the theme has ever hit, because every other image
   is inside a block that zeroes it. */
.article__figure {
  margin: clamp(40px, 5vw, 64px) 0 0;
}
/* max-width, not width. An illustration narrower than the 1080 column
   keeps its own size instead of being blown up to fit; a photograph wider
   than the column comes down to it.

   A CEILING ON THE HEIGHT [Emilie 7 okt], because a standing picture had
   none. The large size is 1024px on the long edge, so a portrait came out
   791 by 1024 and the text began 1559px down the page: the whole opening
   of the article was below the fold on a 900px screen.

   SCALED DOWN, NOT CROPPED. width: auto lets the picture keep its own
   proportion and lose width instead; object-fit would have cut a part of
   an editor's picture away, and a template does not get to decide which
   part. 70vh so the picture never fills a screen on its own, 620px so it
   does not grow without end on a tall one. */
.article__figure img {
  display: block;
  max-width: 100%;
  max-height: min(70vh, 620px);
  width: auto;
  height: auto;
  border-radius: var(--radius-card);
}
.article__caption {
  margin-top: var(--wp--preset--spacing--30);
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--wp--preset--color--text-body);
}

/* ONE COLUMN, NOT TWO. The measure rule under "The content column" reaches
   p, ul and ol but not a heading, so an h2 ran the full 1080 while the
   paragraph under it stopped at 683. Measured at 1440 before this rule.

   THE CAP IS ON THE BOX, NOT ON THE HEADINGS. --text-measure is 68ch, and
   ch is read against the element it is written on: on a 44px h2 the same
   token comes to about 1870px and caps nothing. On the body div, which is
   the 16px text size, it is the 683px the paragraphs already use.

   An article is one column of running text. Anything that needs to be
   wider than the column is the article picture, and that is outside this
   box by design.

   THE CLASS IS DOUBLED to reach the specificity of the content column
   rule, which is .site-main:not(...) > article > :not(.section) and
   counts three classes and a type. Written plainly, this rule lost to it
   and the body stayed at 1080, measured. Doubling is the theme's own way
   of saying "same weight, later in the file"; see .band-head.band-head. */
.site-main--article > article > .article__body.article__body {
  max-width: var(--text-measure);
  margin-top: clamp(40px, 5vw, 64px);
}
.article__body > :first-child {
  margin-top: 0;
}
/* 24px between paragraphs, which is theme.json's own blockGap.

   IT HAS TO BE WRITTEN HERE because WordPress applies blockGap through
   .is-layout-flow > * + *, and the_content() output has no layout container
   around it. The paragraphs fell back to the user agent's 1em: measured at
   16px, against the 24 the rest of the site is built on.

   THE POLICY PAGE IS NOT IN THIS SELECTOR, and the reason is worth a line
   because it was wrong once. Its text is not bare the_content() output: it
   is an acf/textblock block, and that block writes its own rhythm in
   assets/css/blocks/textblock.css. The two were brought to the same 24px
   [Emilie 7 okt] by changing that file, not by adding a selector here that
   would never have matched. */
.article__body > :is(p, ul, ol) {
  margin-block: var(--wp--preset--spacing--50) 0;
}
/* Headings get the air that separates one part of an argument from the
   next. Clearing the sticky header when an anchor jumps to one is the
   root's scroll-padding-top. */
.article__body :is(h2, h3, h4) {
  margin-bottom: var(--wp--preset--spacing--40);
}
.article__body h2 {
  margin-top: clamp(48px, 5vw, 72px);
}
.article__body :is(h3, h4) {
  margin-top: clamp(32px, 3.5vw, 48px);
}

/* ------------------------------------------------------------------
   The article list.

   The posts page, /blogg/. Rows under hairlines, which is the rhythm the
   rest of the site is built on, and no card, no thumbnail and no filter
   row. A list page's job is to let a reader pick, and three lines of type
   do that better than a grid of boxes.
   ------------------------------------------------------------------ */
.blog-head > :first-child {
  margin-top: 0;
}
.blog-head__intro {
  max-width: var(--text-measure);
  margin-top: var(--wp--preset--spacing--50);
}
/* The intro's last paragraph carries the user agent's 1em underneath it.
   The main region is a flex column, so a child of it establishes its own
   formatting context and that margin stays inside the box rather than
   collapsing away; it would add 16px under the head. Stated rather than
   left to collapsing, which is fragile. */
.blog-head__intro > :last-child {
  margin-bottom: 0;
}

.article-list {
  margin: clamp(48px, 5vw, 72px) 0 0;
  padding: 0;
  list-style: none;
}
/* The rule belongs to the row above it as much as to the one below, so it
   is drawn on top of every item and once more under the last. */
.article-list__item {
  padding-block: clamp(28px, 3vw, 40px);
  border-top: 1px solid var(--wp--preset--color--hairline);
}
.article-list__item:last-child {
  border-bottom: 1px solid var(--wp--preset--color--hairline);
}
.article-list__date {
  margin: 0;
  font-size: var(--wp--preset--font-size--brod-liten);
  color: var(--wp--preset--color--text-body);
}
/* Rubrik 1, not the display-2 that theme.json gives an h2. These are
   twelve titles under one another, not twelve section headings, and at
   44px each of them would argue with the page's own h1.

   40ch, not --text-measure. ch is read against the element it is written
   on, so the 68ch token comes to about 1870px on a 28px heading and caps
   nothing: measured, the titles ran the full 1080. A heading measure in ch
   is the theme's own idiom, see .display at 16ch. 40ch measures 690px at
   the 28px this heading is, which puts the titles and the 683px excerpts
   under them in the same column. */
.article-list__title {
  max-width: 40ch;
  margin: var(--wp--preset--spacing--20) 0 0;
  font-size: var(--wp--preset--font-size--rubrik-1);
  line-height: 1.3;
}
/* The link takes the heading's own colour and underlines on hover rather
   than always, because a list where every line is underlined reads as a
   table of contents and not as titles. */
.article-list__title a {
  color: inherit;
  text-decoration: none;
}
.article-list__title a:hover,
.article-list__title a:focus-visible {
  text-decoration: underline;
  text-underline-offset: 4px;
}
.article-list__excerpt {
  margin: var(--wp--preset--spacing--30) 0 0;
  color: var(--wp--preset--color--text-body);
}

/* ------------------------------------------------------------------
   Career page.

   /karriar/, from the design handoff [30 okt]. The job list is a block
   and carries its own stylesheet (assets/css/blocks/job-list.css); this is
   the page around it.
   ------------------------------------------------------------------ */

/* The application: the intro, a ribbon, and the form on a card. One
   column until 1080, where the ribbon has room between the two. */
.job-apply {
  position: relative;
  overflow: hidden;
}
.job-apply__grid {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: clamp(40px, 5vw, 72px);
}
.job-apply__intro {
  max-width: 520px;
}
/* The intro takes focus when a job's button leads here (job-list.js),
   which is a place to read from, not a control. */
.job-apply__intro:focus {
  outline: none;
}
/* What happens to the application: one version for an unsolicited one,
   one for a job, and the choice in the form decides which shows. The page
   script sets .is-job on the section; .has-js keeps both in view when no
   script runs, and in the editor, where an editor needs to reach both. */
.job-apply__about {
  margin-top: var(--wp--preset--spacing--65);
}
.has-js .job-apply:not(.is-job) .job-apply__about--job,
.has-js .job-apply.is-job .job-apply__about--unsolicited {
  display: none;
}
/* rubrik-1, for the reason .trust__title gives: rubrik-2 would be
   smaller than the lead above it. */
.job-apply__subheading {
  margin: 0;
  font-size: var(--wp--preset--font-size--rubrik-1);
  font-weight: 400;
  line-height: 1.25;
  letter-spacing: -0.01em;
}
.job-apply__subheading + .band-head__text {
  margin-top: var(--wp--preset--spacing--30);
}
/* The ground, not #FFFFFF: no surface is white [Emilie 26 okt]. */
.job-apply__card {
  margin-top: 0;
  padding: clamp(24px, 3.2vw, 48px);
  border: 1px solid var(--wp--preset--color--hairline);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--ground);
  --field-surface: var(--wp--preset--color--ground);
  --field-tab: 0;
}
/* The confirmation Gravity Forms puts in the card's place. */
.job-receipt {
  padding: 14px 18px;
  border-radius: var(--radius-button);
  background: var(--status-ok-surface);
  color: var(--status-ok);
  font-size: 13px;
  line-height: 1.6;
}
.job-receipt p {
  margin: 0;
}
.job-receipt strong {
  font-size: 15px;
  font-weight: 500;
}

/* THE RIBBON RISES OUT OF THE FOOTER, as the closing bands' do, but stands
   in a column of its own between the words and the form, as the handoff
   draws it. A pseudo element for the same reason as theirs: decoration an
   editor cannot select or delete, and no alt text to remember.

   The column runs past the section's bottom padding to the footer, and
   the section clips it there, so the figure ends on the boundary. Its top
   fades in; it starts in the middle of the band, not on an edge.

   flow-morkbla.webp is the handoff's flow-figure-4x.png, with a
   transparent ground, so it sits on the surface without a box. */
@media (min-width: 1080px) {
  .job-apply__grid {
    grid-template-columns: minmax(0, 520px) 96px minmax(0, 1fr);
  }
  .job-apply__grid::before {
    content: "";
    grid-column: 2;
    grid-row: 1;
    min-height: 520px;
    margin-bottom: calc(var(--section-pad) * -1);
    /* Sized by the column's width, not the box's height. At auto 112% the
       figure grew with the form, to 120px in the 96px column at 1790 wide,
       and its widest bend (source rows 2369 to 3023 reach column 429 of
       440) was cut off on the right. */
    background: url("assets/media/flow-morkbla.webp?v=2") center bottom / 100% auto no-repeat;
    -webkit-mask-image: linear-gradient(to bottom, transparent, #000 30%);
    mask-image: linear-gradient(to bottom, transparent, #000 30%);
    pointer-events: none;
  }
}

/* ------------------------------------------------------------------
   The integration pair.

   The hero illustration of /integrationer/ [Emilie 6 nov]: two companies,
   each a building and bars, joined through the Syncify mark. No company is
   named (guardrail 7), and the mark is the official white symbol file, not
   redrawn (guardrail 6).

   NO NEW COLOUR. The companies are graphite on the band's graphite deep,
   edged with the dark hairline; the links are the muted ink on dark. No
   cyan: nothing here moves.

   ONE STAGE, ZOOMED TO ITS COLUMN, as the portal window: laid out once at
   480 by 260 and shrunk as a whole, so the links always meet the hub.
   ------------------------------------------------------------------ */
.integration-pair {
  container-type: inline-size;
  margin: 0;
  align-self: center;
}
/* The figure takes the band's right hand side, where the flow figure
   entered. Two figures in one corner is one too many, so the flow goes on
   this band. */
.section--tall:has(.integration-pair)::before {
  display: none;
}
/* THIS HERO CENTRES ITS CONTENT [Emilie 11 nov], an exception to THE
   HEADING STARTS AT THE SAME HEIGHT. Top aligned, the words and the pair
   stood at the top of the 742px floor at 1440 with 186px of empty ground
   under them. Centred in the band's content box, so the header's share of
   the top padding is still kept clear. */
.site-main--bands > section:first-child:has(.integration-pair) {
  align-content: center;
}
@media (min-width: 1024px) {
  .band-head:has(> .integration-pair) {
    grid-template-columns: minmax(0, 1fr) minmax(0, 480px);
    column-gap: var(--wp--preset--spacing--70);
  }
}
.integration-pair__stage {
  position: relative;
  width: 480px;
  height: 260px;
  margin-inline: auto;
  zoom: min(1, tan(atan2(100cqw, 480px)));
}
.integration-pair__company {
  position: absolute;
  top: 20px;
  display: flex;
  flex-direction: column;
  gap: 10px;
  width: 150px;
  height: 220px;
  padding: var(--wp--preset--spacing--50) 22px;
  border: 1px solid var(--wp--preset--color--hairline-dark);
  border-radius: var(--radius-card);
  background: var(--wp--preset--color--graphite);
  color: var(--wp--preset--color--text-on-dark);
}
.integration-pair__company--left { left: 0; }
.integration-pair__company--right { right: 0; }
.integration-pair__company > svg {
  flex: none;
  margin-bottom: var(--wp--preset--spacing--20);
}
/* Bars, not words: nothing on a company is meant to be read. */
.integration-pair__bar {
  display: block;
  height: 6px;
  border-radius: 3px;
  background: var(--text-muted-on-dark);
  opacity: 0.45;
}
.integration-pair__bar:nth-of-type(3) { width: 80%; }
.integration-pair__bar:nth-of-type(4) { width: 60%; }
.integration-pair__bar--title {
  width: 70%;
  height: 8px;
  margin-bottom: 6px;
  background: var(--wp--preset--color--text-on-dark);
  opacity: 0.8;
}
/* A link runs from a company's inner edge to the hub's ring, with a dot
   at the company end where the system is attached. */
.integration-pair__link {
  position: absolute;
  top: 129px;
  width: 50px;
  height: 2px;
  background: var(--text-muted-on-dark);
}
.integration-pair__link--left { left: 150px; }
.integration-pair__link--right { right: 150px; }
.integration-pair__link::before {
  content: "";
  position: absolute;
  top: -4px;
  width: 10px;
  height: 10px;
  border-radius: 50%;
  background: var(--text-muted-on-dark);
}
.integration-pair__link--left::before { left: -5px; }
.integration-pair__link--right::before { right: -5px; }
.integration-pair__hub {
  position: absolute;
  top: 90px;
  left: 200px;
  display: grid;
  place-items: center;
  width: 80px;
  height: 80px;
  border: 2px solid var(--text-muted-on-dark);
  border-radius: 50%;
  background: var(--wp--preset--color--graphite);
}
.integration-pair__hub > img {
  display: block;
  width: 52px;
  height: 52px;
}
