/* MYST-specific overrides for pages migrated to Bootstrap 5 / Inspinia 5.0.1.
   Carried forward from the old myst-v3/css/custom.css and myst-v3/css/style.css
   (Inspinia 4.x) — only the rules actual pages depend on, not vendor boilerplate. */

/* .btn-xs existed in the old Inspinia 4.2.0 theme but was dropped from the
   5.0.1 build entirely. ~60 pages still use it for small action buttons
   (delete icons, activity-log badges, etc.), so without this they silently
   render at full .btn size instead of small. Restored verbatim from the
   pre-upgrade CSS. Remove once those buttons are rebuilt with native BS5
   sizing (.btn-sm). */
.btn-xs {
    font-size: 0.7rem;
    padding: 0.2rem 0.4rem;
}

/* Stacked cards in the same column (e.g. the main item_form card followed by
   the Crosslink card) sit directly next to each other with no gap — the
   theme only spaces cards apart via grid gutters (side-by-side columns), not
   between vertically-stacked siblings in the same column. */
.card + .card {
    margin-top: 1.5rem;
}

/* Long unbreakable strings (source URLs, e-mail addresses, file names) in
   card boxes, e.g. the photo list's "Bron-url" in a narrow side column, ran
   out of the card. "anywhere" (not "break-word") also lowers the min-content
   width, so plain layout tables inside the card shrink to fit and wrap the
   string. Data tables (.table) keep normal wrapping: they scroll horizontally
   (myst-table-scroll) instead of chopping words into fragments. */
.card-body {
    overflow-wrap: anywhere;
}
.card-body .table {
    overflow-wrap: normal;
}

/* Checkbox-only form rows (e.g. Sight item_form's "In maintenance" /
   "Translated" / "Reviewed" / "Online" pattern, used across ~8 Manager
   modules): each checkbox sits alone in its own .mb-3.row (native BS5
   spacing, formerly .form-group.row), so the default 1rem .mb-3 spacing
   (meant for full label+input fields) makes consecutive checkboxes look
   further apart than needed. */
.mb-3.row:has(> .form-check-inline) {
    margin-bottom: 0.5rem;
}

/* These checkboxes are enlarged to 20x20px via an inline style; Bootstrap 5's
   default gap between checkbox and label (.form-check's 1.5em padding-left
   minus the checkbox width) shrinks as the checkbox grows, so give it a bit
   back. */
.form-check-inline > .form-check-input {
    margin-right: 0.5rem;
}

/* Bootstrap 5's default .form-check-input positioning relies on float +a
   negative inline-start margin sized for the *default* ~1em checkbox; the
   20x20px inline-style override above throws that off enough that on some
   real mobile browsers the checkbox renders detached above the label
   instead of aligned with its first line (reported 09-08-2026, Sight
   Manager). Switching the pairing to flex removes the float-based
   positioning entirely, so the checkbox and label are simply two flex
   items aligned to the same top edge regardless of checkbox size or label
   wrapping. */
.form-check-inline {
    display: inline-flex;
    align-items: flex-start;
}
.form-check-inline .form-check-input {
    float: none;
    margin-inline-start: 0;
    flex-shrink: 0;
}

/* Manager header action-button row ("Add new X" / "Home" / "All X" / "My X" /
   "More" — the `.d-flex.flex-wrap...mb-3` row used identically across ~27
   header.php files) is fine on desktop; on phone width it wraps into a stack
   of full-height, full-text buttons. Scoped to phone width only (desktop/
   tablet unchanged, per explicit user request). Buttons that carry an icon
   (`<i>`) collapse to icon-only via the font-size:0-on-parent trick (hides
   the plain text node, the icon gets its own explicit font-size back) so no
   markup change is needed across those 27 files. Icon-less buttons (a few
   headers only have plain-text buttons) just get tighter padding/min-width
   instead, since there's no icon to fall back to. */
@media (max-width: 767.98px) {
    .d-flex.flex-wrap.align-items-center.gap-2.mb-3 .btn {
        min-width: 0;
        padding: 0.375rem 0.6rem;
    }
    .d-flex.flex-wrap.align-items-center.gap-2.mb-3 .btn:has(i) {
        font-size: 0;
    }
    .d-flex.flex-wrap.align-items-center.gap-2.mb-3 .btn:has(i) i {
        font-size: 1rem;
        margin: 0 !important;
    }
    .d-flex.flex-wrap.align-items-center.gap-2.mb-3 .dropdown-toggle > i {
        display: inline;
    }
}

/* The "More"/"Meer" dropdown-toggle button's "..." icon is only meant as the
   icon-only mobile affordance above; on desktop/tablet the button already
   shows the full text, so the icon is redundant there. Root cause of a
   real bug (09-08-2026): this rule and the mobile "display: inline" rule
   above have identical selectors/specificity, so without the min-width
   guard the later rule in source order (this one) always won the cascade
   on mobile too, deleting the icon there as well as the text (which the
   font-size:0 trick above already hides) -- an empty, unusable "More"
   button. Scoping this to desktop/tablet only makes the two rules mutually
   exclusive by breakpoint, no cascade ambiguity. */
@media (min-width: 768px) {
    .d-flex.flex-wrap.align-items-center.gap-2.mb-3 .dropdown-toggle > i {
        display: none;
    }
}

/* Section headings inside cards (page title, "Photos", "Crosslink", "Awards",
   "Units", etc.) all use <h3 class="font-bold"> — at the theme's default h3
   size (~1.39rem) that reads far too large/heavy for what's meant to be a
   compact card header. Sized down closer to h4, still bold enough to stand
   out from the card body. */
h3.font-bold {
    font-size: 1.15rem;
}

/* Activity-log rows ("Latest N activities" widget, include/userlog/userlog.php) had
   no spacing between rows at all, so the action badges appeared to touch each other. */
.stream-small {
    margin-bottom: 0.5rem;
    display: block;
}

/* Manager "Statistics" panels (Sight/Person/Award/News/Users/Articles) show
   each stat's value in a plain <h4> right after a <small class="stats-label">
   label. Sized to match the label's own <small> (0.85em) font-size exactly —
   same parent context, so both resolve to the same pixel size — instead of
   the much larger default h4 size. */
.stats-label + h4 {
    font-size: 0.85em;
    margin-bottom: 1rem;
}

/* Multi-word labels ("Check old articles", "No cemetery link") wrap inside
   the narrow .col-3 stat cells. Without a reserved height, a longer label
   pushes its own number down relative to shorter labels in the same row, so
   the numbers across a row don't line up. A fixed min-height (worst case
   across all Manager stat blocks: 3 wrapped lines, e.g. "Check old
   articles") keeps every number in a row at the same vertical position, and
   the explicit word-break/hyphens reset stops mid-word breaks in very narrow
   columns (mobile).
   Revised 05-10-2026 (user feedback, Artikel Manager): with the text at the
   TOP of that reserved height, short labels ("English") left a big gap above
   their own number, so each number visually belonged to the label of the row
   below it. The text now sits at the BOTTOM (flex-end), directly above its
   number; numbers in a row still line up. */
.stats-label {
    display: flex;
    align-items: flex-end;
    min-height: 3.6em;
    line-height: 1.2;
    overflow-wrap: normal;
    word-break: normal;
    hyphens: none;
}

/* On mobile, the fixed .col-3/.col-4 stat cells (see above) keep their
   desktop column count instead of adapting to the narrow screen, cramming
   labels/numbers into columns too tight to read comfortably. Below the
   sm breakpoint, force every stat cell in a Statistics row to its own full
   line instead — the same 1-per-row list on every Manager that uses this
   shared .stats-label pattern. min-height above is no longer needed once
   stacked (each label has the full row width to itself), so drop it here
   to avoid unnecessary vertical gaps.
   Revised 09-08-2026 (user feedback: the first version put the label above
   the value, doubling the list length): label and value now sit on the
   SAME line as a compact "label ... value" row (flex, value pushed to the
   end), rather than one full-width block per label followed by its own
   full-width block per value. */
@media (max-width: 575.98px) {
    div[class^="col-"]:has(> .stats-label),
    div[class*=" col-"]:has(> .stats-label) {
        flex: 0 0 100%;
        max-width: 100%;
        min-height: 0;
        display: flex;
        justify-content: space-between;
        align-items: baseline;
        gap: 0.75rem;
    }
    .stats-label {
        display: inline;
        min-height: 0;
    }
    .stats-label + h4 {
        margin-bottom: 0;
    }
}

#main {
    background-color: #ffffff;
    color: inherit;
    padding: 0 0 20px 0;
    font-family: "open sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 13px;
    margin: 25px;
    margin-bottom: 65px;
}
#main h2 {
    background-color: #ffffff;
    color: #676a6c;
    margin: 0;
    margin-bottom: 15px;
    padding: 15px 15px 7px;
    min-height: 48px;
    font-size: 14px;
    font-weight: 600;
    border-top: 2px solid #e7eaec;
    border-bottom: 1px solid #e7eaec;
}

.nav-second-level li {
    min-width: 180px;
}

.table-topics {
    vertical-align: middle;
}

.normal-text-link {
    color: inherit;
    text-decoration: none;
}

.normal-text-link:hover {
    text-decoration: underline;
}

/* Forum */
.forum-item {
    margin: 10px 0;
    padding: 10px 0 20px;
    border-bottom: 1px solid #f1f1f1;
}
.forum-container,
.forum-post-container {
    padding: 30px !important;
}
.forum-item small {
    color: #999;
}
.forum-item .forum-sub-title {
    color: #999;
    margin-left: 50px;
}
.forum-title {
    margin: 15px 0 15px 0;
}
.forum-info {
    text-align: center;
}
.forum-desc {
    color: #999;
}
.forum-icon {
    float: left;
    width: 30px;
    margin-right: 20px;
    text-align: center;
}
a.forum-item-title {
    color: inherit;
    display: block;
    font-size: 18px;
    font-weight: 600;
}
a.forum-item-title:hover {
    color: inherit;
}
.forum-icon .fa {
    font-size: 30px;
    margin-top: 8px;
    color: #9b9b9b;
}
.forum-item.active .fa {
    color: var(--theme-link-color);
}
.forum-item.active a.forum-item-title {
    color: var(--theme-link-color);
}
@media (max-width: 992px) {
    .forum-info {
        margin: 15px 0 10px 0;
        display: none;
    }
    .forum-desc {
        float: none !important;
    }
}

/* Bootstrap 5 only draws the dropdown chevron on <select class="form-select">;
   unlike Bootstrap 4, a plain <select> or <select class="form-control"> gets no
   arrow at all in BS5, so it doesn't read as a dropdown. Systemic pattern across
   MYST: of ~664 <select> tags in the codebase, only 1 already uses form-select.
   CSS-only fix (same chevron SVG/positioning as .form-select in app.min.css),
   scoped to skip elements that already have their own chevron, so none of the
   100+ affected files needed editing. select2-enhanced selects are unaffected
   (select2 hides the native <select> and renders its own widget). */
select:not(.form-select) {
    -webkit-appearance: none;
    -moz-appearance: none;
    appearance: none;
    background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath fill='none' stroke='%23343a40' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/%3E%3C/svg%3E");
    background-repeat: no-repeat;
    background-position: right 0.77rem center;
    background-size: 14px 10px;
    padding-right: 2.31rem;
}

/* Forum post bodies are free-text and often contain long, unbroken URLs
   (plain text or hyperlinked). Flex children default to min-width: auto, so
   long unbreakable content keeps the flex item (and with it the post card
   and the page's layout viewport on mobile) from shrinking below the URL's
   own width, no matter what overflow-wrap says. min-width: 0 lets the flex
   item actually shrink to the available space; overflow-wrap then wraps the
   long string inside it instead of overflowing. */
.forum-post-flex {
    min-width: 0;
}
.forum-post-content {
    overflow-wrap: anywhere;
}

/* Mobile forum posts (topic.php): the desktop avatar-left/content-right flex
   row reserves the avatar's column width for the post's FULL height, so a
   multi-line post stays indented behind an empty gap next to a ~40px avatar
   for every line after the first -- on a ~375px phone that wastes a third of
   the screen on nothing. Below md, drop the flex row for a flow-root block
   with the avatar floated left instead: text still wraps beside the avatar
   for its own height, then reclaims the full row width once past it, the
   same way a printed byline photo works. flow-root (not plain block) keeps
   the float contained inside each post's own border, so it can't leak into
   the next post below it. Borders/padding around each post are also dropped
   in favour of a single hairline separator, since a bordered+padded box per
   post eats more of the already-narrow width than it's worth on mobile.
   The quoted-reply block (.forum-post-quote) keeps its own bg-light/rounded/
   p-3 box at every width instead -- that box IS the "this is a quote" signal
   now (replacing the old indent+muted-text treatment, which read as washed-out
   and easy to miss on mobile), so unlike .forum-post-row it must not lose its
   padding/background on small screens. */
@media (max-width: 767.98px) {
    .forum-post-row,
    .forum-post-quote {
        display: flow-root !important;
    }
    .forum-post-row {
        border: none !important;
        border-radius: 0 !important;
        border-bottom: 1px solid var(--theme-border-color);
        padding: 0.75rem 0 !important;
    }
    .forum-post-row > .flex-shrink-0,
    .forum-post-quote > .flex-shrink-0 {
        float: left;
        margin-right: 0.5rem;
    }
    .forum-post-row > .forum-post-flex,
    .forum-post-quote > .forum-post-flex {
        margin-left: 0 !important;
    }
}

/* Icon-only buttons (e.g. the trash-icon delete button in a modal-footer, or
   the bookmark/cog Follow/Unfollow/Edit-topic buttons in the forum topic
   header) render ~6.5px shorter than their text-content sibling buttons.
   Root cause: .btn is a flex container, so its lone <i> child is a flex item
   and gets "blockified" per the CSS Display spec — its own line-height:1
   (from Font Awesome's .fa rule) then governs the flex item's height instead
   of the button's own line-height:1.5 that text content uses. Giving the
   icon the button's line-height restores equal height. Applied globally
   (not just .modal-footer) since the same DOM shape causes the same bug
   anywhere an icon-only button sits next to a text button. */
.btn > i:only-child {
    line-height: 1.5;
}

/* Summernote toolbar buttons render with Bootstrap's default btn-outline-secondary
   (a light-blue accent, #1c84c6) until item_form.php's onInit callback swaps the
   class to btn-light. That swap runs once, over whatever buttons already exist at
   init time — buttons Summernote creates later (dropdown/popover contents, e.g.
   the font-size or paragraph-alignment menus) never get swapped and keep the blue.
   CSS-only override forces the intended light-grey look on every .note-btn
   regardless of when it's created, using the same variables .btn-light itself
   resolves to, so this can never drift out of sync with that class visually.
   Resting background is transparent rather than --theme-light: .note-toolbar's own
   backdrop is a translucent grey overlay (hsla(0,0%,50%,.114) from summernote-bs5.min.css),
   not solid --theme-light — a solid fill made idle buttons a visibly different,
   slightly-blue-tinted rectangle against that grey bar. Transparent lets each button
   blend into whatever surface it's actually on (toolbar bar or popover), while hover/
   active still get a solid, visibly distinct fill. */
.note-editor .note-btn,
.note-popover .note-btn {
    --theme-btn-color: var(--theme-dark);
    --theme-btn-bg: transparent;
    --theme-btn-border-color: transparent;
    --theme-btn-hover-color: var(--theme-primary);
    --theme-btn-hover-bg: var(--theme-light);
    --theme-btn-hover-border-color: transparent;
    --theme-btn-active-bg: var(--theme-tertiary-bg);
    --theme-btn-active-color: var(--theme-tertiary-color);
    --theme-btn-active-border-color: var(--theme-tertiary-bg);
}

/* Mobiel hamburgermenu opende de sidebar niet (23-08-2026, gemeld via de
   forum-mobiel-inventarisatie, zie action-log.md). Root cause: app.min.css's
   eigen offcanvas-regels (html[data-sidenav-size=offcanvas] .sidenav-menu,
   met een tegenhanger voor .sidebar-enable die de margin terugzet naar 0)
   hebben op zich de juiste CSS-specificiteit, maar de open/dicht-toestand
   bleek op deze browser-versie onbetrouwbaar zodra de meegeleverde
   `transition: all .25s ease-in-out` erbij zit — geverifieerd via een
   losse test: exact dezelfde twee regels werken wél correct op een
   geïsoleerd testelement, en zonder de transition-regel werkt het ook op
   de echte sidebar. Vermoedelijk een browser-eigenaardigheid met
   transities op een calc()+custom-property-waarde
   (--theme-sidenav-width), niet iets om verder te repareren aan de kant
   van dit project. Transitie hier bewust uitgezet (geen animatie meer bij
   open/dicht, maar wél betrouwbaar werkend) i.p.v. de vendor-regel zelf
   aan te passen. */
html[data-sidenav-size="offcanvas"] .sidenav-menu {
    transition: none;
}

/* Mobiele-bruikbaarheidsaudit (08-09-2026, bevinding 3): topbar-icoonknoppen
   (menu-toggle, zoeken, dark-mode, taal, meldingen) waren 32-38px breed op mobiel,
   onder de aanbevolen 44px-aanraakdoelgrootte. Hoogte was al voldoende (volle
   topbar-hoogte); alleen min-width omhoog volstaat, .topbar-link centreert zijn
   icoon al zelf (justify-content/align-items: center). */
@media (max-width: 767.98px) {
    .topbar-link {
        min-width: 44px;
    }
    /* Menuknop en zoek-icoon (.btn-icon, 38x38) kwamen op 375 px niet aan 44 px (gemeten 19-11-2026) en
       stonden zo dicht tegen de rest dat ze er visueel tegenaan plakten; nu 44x44 met ruimte ertussen. */
    .app-topbar .sidenav-toggle-button,
    .app-topbar .topnav-toggle-button,
    .app-topbar .btn-icon {
        min-width: 44px;
        min-height: 44px;
    }
    .app-topbar .topbar-menu > .d-flex:first-child {
        gap: .5rem;
    }
}

/* Topbar op smalle telefoons (08-10-2026, gezien 02-10 op 375px: scrollWidth 407). De vaste
   knoppen (44px, zie hierboven) passen net; een statusitem (onderhoudsbadge of "Account
   overnemen", .topbar-status) duwt de rij buiten beeld. Alleen dan, en alleen < 576px: eerst
   de licht/donker-knop weg, bij twee statusitems ook de taalknop. Beide zijn tijdelijke
   beheerderssituaties; de knoppen keren terug zodra het statusitem weg is. */
@media (max-width: 575.98px) {
    .topbar-right:has(.topbar-status) .topbar-theme-toggle,
    .topbar-right:has(.topbar-status ~ .topbar-status) .topbar-lang {
        display: none !important;
    }
}

/* Voettekst die rechtstreeks in .wrapper staat (niet in .content-page): de negatieve zijmarges van .footer
   (-0.625rem, bedoeld om de opvulling van .content-page op te heffen) duwen hem dan 10 px buiten beeld, dus
   de hele pagina scrolt horizontaal. Gemeten 19-11-2026 op 375 px bij 005/0143, waar een overtollige </div>
   .content-page eerder sluit. Algemeen gedicht, ook voor pagina's met vergelijkbare markup. */
.wrapper > .footer {
    margin-left: 0;
    margin-right: 0;
}

/* Mobiele-bruikbaarheidsaudit, bevinding 1 (herbouwd 29-09-2026): een tabel die breder is
   dan het scherm vervaagt aan de kant waar nog kolommen staan. De klassen zet
   assets/js/myst-table-scroll.js, en alleen bij echte overloop (de statische schaduw van
   17-09 stond ook op desktop en is daarom teruggedraaid). mask-image i.p.v. een gradient
   in een kleur: werkt op elke kaart-achtergrond en in dark mode zonder eigen kleurtoken. */
.table-responsive.myst-scroll-right {
    -webkit-mask-image: linear-gradient(to right, #000 calc(100% - 32px), transparent);
    mask-image: linear-gradient(to right, #000 calc(100% - 32px), transparent);
}
.table-responsive.myst-scroll-left {
    -webkit-mask-image: linear-gradient(to left, #000 calc(100% - 32px), transparent);
    mask-image: linear-gradient(to left, #000 calc(100% - 32px), transparent);
}
.table-responsive.myst-scroll-left.myst-scroll-right {
    -webkit-mask-image: linear-gradient(to right, transparent, #000 32px, #000 calc(100% - 32px), transparent);
    mask-image: linear-gradient(to right, transparent, #000 32px, #000 calc(100% - 32px), transparent);
}

/* Forum-mobiel-inventarisatie (23-08-2026, uitgevoerd 28-09-2026): Summernote-
   toolbarknoppen waren 34x30px op mobiel, onder de 44px-aanraakdoelgrootte (zelfde norm
   als .topbar-link hierboven). Geldt voor elke Summernote-editor, niet alleen het forum.
   Alleen de maat; kleur/achtergrond blijven van de .note-btn-regel hierboven. */
@media (max-width: 767.98px) {
    .note-editor .note-toolbar .note-btn {
        min-width: 44px;
        min-height: 44px;
    }
}

/* Support Center look & feel-voorstel (18-09-2026, gebruikersopdracht), pilot voor
   een herbruikbaar leespatroon -- zie docs/features/support-center-look-and-feel.md.
   Bedoeld voor hergebruik op elk scherm dat ongestylede Summernote-HTML toont
   (Forum/Artikelen/Nieuws volgen later, strangler-fig). Alleen bestaande
   bestaande Inspinia-theme-tokens (--theme-primary/--theme-border-color -- dit
   thema gebruikt zijn eigen --theme-*-namespace, niet Bootstrap's --bs-*-namen,
   geverifieerd via de gerenderde pagina), geen nieuwe kleuren. */

/* Leesbare content-typografie voor lange, door Summernote geschreven tekst */
.rich-content {
    font-size: 1.02rem;
    line-height: 1.75;
    max-width: 68ch;
}
.rich-content p {
    margin-bottom: 1.1rem;
}
.rich-content h2,
.rich-content h3 {
    margin-top: 1.75rem;
    margin-bottom: .75rem;
}
.rich-content ul,
.rich-content ol {
    margin-bottom: 1.1rem;
    padding-left: 1.4rem;
}
.rich-content li {
    margin-bottom: .4rem;
}
.rich-content img {
    border-radius: .5rem;
    margin: .5rem 0 1rem;
}

/* Genummerde stappen: een gewone <ol> (bestaande Summernote-toolbarknop, geen
   nieuw veld) krijgt automatisch ronde genummerde markers in de huisstijlkleur. */
.rich-content > ol {
    list-style: none;
    padding-left: 0;
    counter-reset: step;
}
.rich-content > ol > li {
    counter-increment: step;
    position: relative;
    padding-left: 2.75rem;
    min-height: 2rem;
}
.rich-content > ol > li::before {
    content: counter(step);
    position: absolute;
    left: 0;
    top: 0;
    width: 1.9rem;
    height: 1.9rem;
    border-radius: 50%;
    background: var(--theme-primary);
    color: #fff;
    font-weight: 600;
    font-size: .85rem;
    display: flex;
    align-items: center;
    justify-content: center;
}

/* Domeintegels (bv. Support Center-index): kaartgrid i.p.v. platte lijst */
.support-domain-tile {
    height: 100%;
    transition: box-shadow .15s ease-in-out, transform .15s ease-in-out;
}
.support-domain-tile:hover {
    box-shadow: 0 .5rem 1.25rem rgba(0, 0, 0, .08);
    transform: translateY(-2px);
}
.support-domain-tile .tile-icon {
    width: 3rem;
    height: 3rem;
    border-radius: .6rem;
    display: flex;
    align-items: center;
    justify-content: center;
    font-size: 1.4rem;
}

/* Categorie-koppen in een artikelenlijst: badge-pill + lijn i.p.v. kale <h4> */
.support-cat-heading {
    display: flex;
    align-items: center;
    gap: .6rem;
    margin: 1.75rem 0 .75rem;
}
.support-cat-heading:first-child {
    margin-top: 0;
}
.support-cat-heading .line {
    flex: 1;
    height: 1px;
    background: var(--theme-border-color);
}

/* Artikelpagina Support Center (11-10-2026, naar help.etsy.com): navigatie en artikel op
   één wit vlak. Op mobiel staat de navigatie onder het artikel (lijn erboven), vanaf lg
   links ernaast (lijn rechts) en blijft hij staan bij scrollen. */
.support-article-nav {
    border-top: 1px solid var(--theme-border-color);
}
@media (min-width: 992px) {
    .support-article-nav {
        border-top: 0;
        border-right: 1px solid var(--theme-border-color);
    }
    .support-article-nav .sticky-nav {
        position: sticky;
        top: calc(var(--theme-topbar-height, 65px) + 1rem);
        max-height: calc(100vh - var(--theme-topbar-height, 65px) - 2rem);
        overflow-y: auto;
    }
}

/* Overstap van skin "minimal" naar "neon" (21-09-2026, leesbaarheidsklacht: witte
   kaarten op witte pagina-achtergrond) -- Neon geeft wel het gewenste contrast
   tussen pagina- en kaartachtergrond, maar heeft een eigen --theme-primary
   (#3f5098, navyblauw) i.p.v. het bestaande MYST-merkgroen. Hier teruggezet naar
   het merkgroen zodat alleen het achtergrondcontrast verandert, niet de
   merkidentiteit (knoppen/links/actieve menu-items/grafieken). Waarden
   overgenomen uit het vorige "minimal"-skin-blok in app.css.
   11-10-2026: terug naar "minimal" als standaardskin (neon oogde te retro). De blokken
   hieronder gelden daarom voor beide skins; minimal-specifieke aanvullingen (o.a. de
   lichtgrijze pagina-achtergrond tegen de klacht van 21-09) staan er direct onder. */
html:is([data-skin="neon"], [data-skin="minimal"]) {
    /* Primair groen donkerder voor WCAG AA (09-10-2026, optie A uit de voorbeeldpagina,
       keuze gebruiker): #1ab394 -> #13816b. 14-10-2026: daarna overgenomen van de towv3-repo
       (tracesofwar.com, src/input.css): #147a45 (wit 5,4:1), donker #0f5c34, op donker
       #6fd39a als tekst en #173a28 als vlak. Zie het dark-blok hieronder. */
    --theme-primary: #147a45;
    --theme-primary-rgb: 20, 122, 69;
    --theme-primary-bg-subtle: rgba(20, 122, 69, 0.15);
    --theme-primary-border-subtle: rgba(20, 122, 69, 0.3);
    --theme-primary-text-emphasis: #0f5c34;
    --theme-chart-primary: #147a45;
    --theme-chart-primary-rgb: 20, 122, 69;
    --theme-link-color: #6fd39a;
    --theme-link-hover-color: #cdeedb;
    /* Info-knop (09-10-2026, optie F): #5fc4be -> #2f7f7a, witte tekst 2,07 -> 4,73.
       Zelfde aanpak als primair: als tekst op donker blijft #5fc4be (dark-blok). */
    --theme-info: #2f7f7a;
    --theme-info-rgb: 47, 127, 122;
    --theme-info-bg-subtle: rgba(47, 127, 122, 0.15);
    --theme-info-border-subtle: rgba(47, 127, 122, 0.3);
    --theme-info-text-emphasis: #256561;
}

/* WCAG-kleurcontrast (08-10-2026, akkoord gebruiker): gedempte tekst, groen en
   linkkleur donkerder tot ze AA halen (4,5:1). Zelfde tint, alleen lichtheid.
   Light en dark bewust gescheiden: anders overschrijft dit blok ook de dark-waarden.
   --theme-primary is op 09-10-2026 apart aangepast (zie het blok hierboven). Zie
   docs/features/wcag-toegankelijkheidsaudit.md, "Kleurcontrast". */
html:is([data-skin="neon"], [data-skin="minimal"]):not([data-bs-theme="dark"]) {
    --theme-secondary-color: #5e6c82;           /* was #9ba6b7: 2,46 -> 5,33 op wit */
    --theme-secondary-color-rgb: 94, 108, 130;
    --theme-success: #407357;                   /* was #7fb898: wit erop 2,28 -> 5,51 */
    --theme-success-rgb: 64, 115, 87;
    --theme-success-text-emphasis: #3e5b4b;     /* was #5f8a72 (hover btn-success) */
    --theme-success-bg-subtle: rgba(64, 115, 87, 0.15);
    --theme-success-border-subtle: rgba(64, 115, 87, 0.3);
    --theme-link-color: #0f5c34;                /* towv3 brand-dark, 8:1 op wit */
    --theme-link-color-rgb: 15, 92, 52;
    --theme-link-hover-color: #0a3f24;
    --theme-link-hover-color-rgb: 10, 63, 36;
    --theme-emphasis-color: rgba(76, 76, 92, 0.85); /* was .75 (footer): 4,01 -> 5,14 */
}
/* Dark: gedempte tekst en linkkleur halen al AA. Groen als achtergrond (witte tekst)
   wordt donkerder; groen als TEKST op donker houdt de oude kleur via een eigen token. */
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] {
    --theme-success: #407357;
    --theme-success-rgb: 64, 115, 87;
    --theme-success-text-emphasis: #3e5b4b;
    --myst-success-text-dark: #7fb898;
    --theme-primary-text-emphasis: #6fd39a;
    --theme-primary-bg-subtle: #173a28;         /* towv3 brand-light in donkere modus */
    --myst-primary-text-dark: #6fd39a;          /* #147a45 als tekst op donker te laag; towv3 gebruikt #6fd39a */
    --theme-info-text-emphasis: #5fc4be;
    --myst-info-text-dark: #5fc4be;             /* #2f7f7a als tekst op donker: 3,59, te laag */
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] :is(.text-info, .link-info) {
    color: var(--myst-info-text-dark) !important;
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .badge-soft-info {
    --theme-badge-color: var(--myst-info-text-dark);
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] :is(.btn-outline-info, .btn-soft-info) {
    --theme-btn-color: var(--myst-info-text-dark);
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .btn-info {
    --theme-btn-hover-bg: #256561;
    --theme-btn-hover-border-color: #256561;
    --theme-btn-active-bg: #256561;
    --theme-btn-active-border-color: #256561;
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] :is(.text-primary, .link-primary) {
    color: var(--myst-primary-text-dark) !important;
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .badge-soft-primary {
    --theme-badge-color: var(--myst-primary-text-dark);
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] :is(.btn-outline-primary, .btn-soft-primary) {
    --theme-btn-color: var(--myst-primary-text-dark);
}
/* Hover/active van .btn-primary leest --theme-primary-text-emphasis; die is in dark licht
   (tekstkleur), dus hier vast het donkere groen zodat de witte tekst leesbaar blijft. */
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .btn-primary {
    --theme-btn-hover-bg: #0f5c34;
    --theme-btn-hover-border-color: #0f5c34;
    --theme-btn-active-bg: #0f5c34;
    --theme-btn-active-border-color: #0f5c34;
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] :is(.text-success, .link-success) {
    color: var(--myst-success-text-dark) !important;
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .badge-soft-success {
    --theme-badge-color: var(--myst-success-text-dark);
}
html:is([data-skin="neon"], [data-skin="minimal"])[data-bs-theme="dark"] .btn-outline-success {
    --theme-btn-color: var(--myst-success-text-dark);
}

/* Skin "minimal" (11-10-2026, keuze gebruiker): de blokken hierboven zetten groen/info
   op neon's gedempte tinten; voor minimal dezelfde aanpak (alleen lichtheid omlaag tot
   witte tekst AA haalt), maar vanuit minimal's eigen frisse tinten:
   success #0acf97 -> #067f5d (wit 2,02 -> 5,0), info #23c6c8 -> #167c7d (wit 2,10 -> 4,98).
   Als tekst op donker blijven de originele tinten (8,4 / 8,1 op de dark-achtergrond). */
html[data-skin="minimal"] {
    --theme-info: #167c7d;
    --theme-info-rgb: 22, 124, 125;
    --theme-info-bg-subtle: rgba(22, 124, 125, 0.15);
    --theme-info-border-subtle: rgba(22, 124, 125, 0.3);
    --theme-info-text-emphasis: #105b5c;
}
html[data-skin="minimal"]:not([data-bs-theme="dark"]) {
    /* Pagina lichtgrijs i.p.v. wit, zodat witte kaarten loskomen (klacht 21-09-2026).
       #f7f7fb is minimal's eigen hover-achtergrond van het menu, geen nieuwe kleur. */
    --theme-body-bg: #f7f7fb;
    --theme-body-bg-rgb: 247, 247, 251;
    --theme-success: #067f5d;
    --theme-success-rgb: 6, 127, 93;
    --theme-success-text-emphasis: #055e45;
    --theme-success-bg-subtle: rgba(6, 127, 93, 0.15);
    --theme-success-border-subtle: rgba(6, 127, 93, 0.3);
}
/* Actief/hover menu-item: minimal zet #1ab394 op #f7f7fb (2,5:1); het donkere groen haalt AA. */
html[data-skin="minimal"][data-menu-color="light"]:not([data-bs-theme="dark"]) {
    --theme-sidenav-item-hover-color: #147a45;
    --theme-sidenav-item-active-color: #147a45;
}
html[data-skin="minimal"][data-bs-theme="dark"] {
    --theme-success: #067f5d;
    --theme-success-rgb: 6, 127, 93;
    --theme-success-text-emphasis: #055e45;
    --myst-success-text-dark: #0acf97;
    --theme-info-text-emphasis: #23c6c8;
    --myst-info-text-dark: #23c6c8;
}
html[data-skin="minimal"][data-bs-theme="dark"] .btn-info {
    --theme-btn-hover-bg: #105b5c;
    --theme-btn-hover-border-color: #105b5c;
    --theme-btn-active-bg: #105b5c;
    --theme-btn-active-border-color: #105b5c;
}

/* Danger/warning/secondary (11-10-2026, zelfde aanpak als success/info hierboven):
   minimal's tint, alleen donkerder tot witte tekst AA haalt, ook op de grijze pagina.
   danger #ed5565 -> #dd172c (wit 3,45 -> 4,96), warning #f8ac59 -> #a95b07 (1,90 -> 5,02),
   secondary #1c84c6 -> #1976b1 (4,07 -> 4,92). Hover/active ~7,5:1.
   Als tekst op donker: danger en warning houden de originele tint (4,9 / 8,9); secondary
   haalde ook origineel geen AA op donker (4,18) en wordt daar iets lichter (#1e8fd6, 4,8). */
html[data-skin="minimal"] {
    --theme-danger: #dd172c;
    --theme-danger-rgb: 221, 23, 44;
    --theme-danger-bg-subtle: rgba(221, 23, 44, 0.15);
    --theme-danger-border-subtle: rgba(221, 23, 44, 0.3);
    --theme-danger-text-emphasis: #a91222;
    --theme-warning: #a95b07;
    --theme-warning-rgb: 169, 91, 7;
    --theme-warning-bg-subtle: rgba(169, 91, 7, 0.15);
    --theme-warning-border-subtle: rgba(169, 91, 7, 0.3);
    --theme-warning-text-emphasis: #804505;
    --theme-secondary: #1976b1;
    --theme-secondary-rgb: 25, 118, 177;
    --theme-secondary-bg-subtle: rgba(25, 118, 177, 0.15);
    --theme-secondary-border-subtle: rgba(25, 118, 177, 0.3);
    --theme-secondary-text-emphasis: #135986;
}
html[data-skin="minimal"][data-bs-theme="dark"] {
    --myst-danger-text-dark: #ed5565;
    --myst-warning-text-dark: #f8ac59;
    --myst-secondary-text-dark: #1e8fd6;
}
html[data-skin="minimal"][data-bs-theme="dark"] .text-danger,
html[data-skin="minimal"][data-bs-theme="dark"] .link-danger {
    color: var(--myst-danger-text-dark) !important;
}
html[data-skin="minimal"][data-bs-theme="dark"] .text-warning,
html[data-skin="minimal"][data-bs-theme="dark"] .link-warning {
    color: var(--myst-warning-text-dark) !important;
}
html[data-skin="minimal"][data-bs-theme="dark"] .text-secondary,
html[data-skin="minimal"][data-bs-theme="dark"] .link-secondary {
    color: var(--myst-secondary-text-dark) !important;
}
html[data-skin="minimal"][data-bs-theme="dark"] .badge-soft-danger { --theme-badge-color: var(--myst-danger-text-dark); }
html[data-skin="minimal"][data-bs-theme="dark"] .badge-soft-warning { --theme-badge-color: var(--myst-warning-text-dark); }
html[data-skin="minimal"][data-bs-theme="dark"] .badge-soft-secondary { --theme-badge-color: var(--myst-secondary-text-dark); }
html[data-skin="minimal"][data-bs-theme="dark"] :is(.btn-outline-danger, .btn-soft-danger) { --theme-btn-color: var(--myst-danger-text-dark); }
html[data-skin="minimal"][data-bs-theme="dark"] :is(.btn-outline-warning, .btn-soft-warning) { --theme-btn-color: var(--myst-warning-text-dark); }
html[data-skin="minimal"][data-bs-theme="dark"] :is(.btn-outline-secondary, .btn-soft-secondary) { --theme-btn-color: var(--myst-secondary-text-dark); }
/* Hover/active van de gevulde knoppen vast donker, net als bij .btn-info/.btn-primary. */
html[data-skin="minimal"][data-bs-theme="dark"] .btn-danger {
    --theme-btn-hover-bg: #a91222; --theme-btn-hover-border-color: #a91222;
    --theme-btn-active-bg: #a91222; --theme-btn-active-border-color: #a91222;
}
html[data-skin="minimal"][data-bs-theme="dark"] .btn-warning {
    --theme-btn-hover-bg: #804505; --theme-btn-hover-border-color: #804505;
    --theme-btn-active-bg: #804505; --theme-btn-active-border-color: #804505;
}
html[data-skin="minimal"][data-bs-theme="dark"] .btn-secondary {
    --theme-btn-hover-bg: #135986; --theme-btn-hover-border-color: #135986;
    --theme-btn-active-bg: #135986; --theme-btn-active-border-color: #135986;
}

/* Dashboard-onderzoek (21-09-2026, gebruikerswens): het Dashboard voelde
   "gepropt" met kleine tekst t.o.v. Inspinia's eigen voorbeeldwidgets
   (webapplayers.com/inspinia) -- meer witruimte, grotere cijfers, icoon in
   een gekleurde blokje i.p.v. los grijs icoon. Bewust ALLEEN toegepast
   binnen .myst-dashboard (wrapper om de pagina-inhoud van 001/0126), niet
   systeembreed: de gedeelde .stats-label/.card-body-opmaak op alle andere
   Manager-pagina's blijft ongewijzigd (harde eis: één gedeeld
   designsysteem, scope hier bewust beperkt gehouden, zie decisions-log.md). */
.myst-dashboard .card-body {
    padding: 1.5rem;
}
.myst-dashboard h3.font-bold {
    font-size: 1.3rem;
}

/* "Mijn content"-kaarten: zelfde icoon-in-blokje-patroon als
   .support-domain-tile .tile-icon hierboven, kleuren uit de bestaande
   --theme-primary-*-tokens (geen nieuwe kleuren). */
.dash-stat-card .card-body {
    display: flex;
    align-items: center;
    gap: .75rem;
    padding: .75rem 1rem;
}
.dash-stat-icon {
    width: 2.25rem;
    height: 2.25rem;
    border-radius: .5rem;
    display: flex;
    align-items: center;
    justify-content: center;
    font-size: 1.15rem;
    flex-shrink: 0;
    background: var(--theme-primary-bg-subtle);
    color: var(--theme-primary-text-emphasis);
}
.dash-stat-label {
    display: block;
    color: #676a6c;
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}
.dash-stat-card .card-body > div:last-child {
    min-width: 0; /* anders kapt de label-ellipsis niet af */
}
/* Compact sinds 05-10-2026: alle zes Mijn content-blokken op één regel (xl). */
.dash-stat-value {
    font-size: 1.25rem;
    line-height: 1.2;
}

/* Hele tabelrij klikbaar (mobiele-bruikbaarheidsaudit bevinding 2, 08-10-2026): gedrag in
   assets/js/myst-row-link.js; hover-kleur komt van de bestaande .table-hover. */
tr[data-href] {
    cursor: pointer;
}

/* Toegankelijkheid (09-10-2026, docs/features/schermlezer-toegankelijkheid.md).
   Het Inspinia-thema zet het focuskader overal op 0 (outline: 0, box-shadow 0 0 0 0), waardoor je
   met Tab niet ziet waar je bent. Eén zichtbaar kader in MYST-groen, alleen bij toetsenbordfocus
   (:focus-visible), dus muisklikken op knoppen houden hun huidige uiterlijk. !important is nodig omdat
   app.min.css zelf `a, button { outline: none !important; }` zet; zonder !important wint die altijd. */
a:focus-visible,
button:focus-visible,
.btn:focus-visible,
.nav-link:focus-visible,
.side-nav-link:focus-visible,
.dropdown-item:focus-visible,
.page-link:focus-visible,
.form-control:focus-visible,
.form-select:focus-visible,
.form-check-input:focus-visible,
.note-editable:focus-visible,
[tabindex]:focus-visible {
    outline: 2px solid var(--theme-primary) !important;
    outline-offset: 2px;
}
/* Doel van de "Naar hoofdinhoud"-link: geen kader rond de hele pagina-inhoud. */
#main-content:focus,
#main-content:focus-visible {
    outline: none !important;
}
/* "Naar hoofdinhoud"-link (include/body_top2.php): onzichtbaar tot hij focus krijgt
   (.visually-hidden-focusable), dan linksboven boven de topbar (z-index 1001/1005). */
.myst-skip-link:focus {
    position: fixed;
    top: .5rem;
    left: .5rem;
    z-index: 2000;
}
/* "?"-knop met helptekst naast een veldlabel (include/field_help.php, assets/js/myst-field-help.js).
   Minstens 24x24 px tikdoel (WCAG 2.5.8), icoon in de gedempte tekstkleur, primaire kleur bij
   aanwijzen/openen. Popover iets breder dan standaard, voor opsommingen zoals de uploadeisen. */
.myst-field-help {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 24px;
    min-height: 24px;
    padding: 0;
    margin-left: .25rem;
    vertical-align: middle;
    line-height: 1;
    font-size: 1.1rem;
    color: var(--bs-secondary-color);
    text-decoration: none;
}
.myst-field-help:hover,
.myst-field-help[aria-expanded="true"] {
    color: var(--theme-primary);
}
.myst-field-help-popover {
    --bs-popover-max-width: 320px;
}
.myst-field-help-popover .popover-body > :last-child {
    margin-bottom: 0;
}

/* Bootstrap-utility .w-auto ontbreekt in de thema-build (app.min.css), terwijl filterbalken
   hem gebruiken (026/0147, 023/0170, 027/0171): zonder deze regel rekt .form-select (width:
   100%) over de hele regel uit. max-width houdt lange opties binnen een telefoonscherm.
   Toegevoegd 13-10-2026. */
.w-auto {
    width: auto !important;
}
.form-select.w-auto {
    max-width: 100%;
}

/* Leaflet-panelen en -knoppen hebben z-index tot 1000 en vielen daardoor over dropdownmenu's
   (tandwielmenu Bezienswaardigheid Manager, bèta LK-06/JV-16/AT-04). isolation houdt die
   z-indexen binnen de kaart zelf. Toegevoegd 27-10-2026. */
.leaflet-container {
    isolation: isolate;
}

/* Menu-markering huidige pagina (bèta LK-11, 27-10-2026): de actieve optie in de zijbalk was alleen
   licht groen op wit (ca. 2,4:1) en dus bijna niet te zien. Nu: gekleurd vlak, dikke balk links, vet
   en donkere tekst (ca. 6:1, WCAG AA); in donker thema een heldere tekst op het donkere vlak.
   Geldt voor de optie-links; de site-kop (bovenste niveau) houdt zijn bestaande stijl. */
.side-nav .side-nav-item .side-nav-item.active > a.side-nav-link,
.side-nav .sub-menu .side-nav-item.active > a.side-nav-link {
    color: #0b5c4c !important;
    background-color: var(--theme-sidenav-item-active-bg);
    box-shadow: inset 4px 0 0 var(--theme-primary, #1ab394);
    font-weight: 700;
}
html[data-menu-color="dark"] .side-nav .side-nav-item .side-nav-item.active > a.side-nav-link,
html[data-menu-color="dark"] .side-nav .sub-menu .side-nav-item.active > a.side-nav-link {
    color: #ffffff !important;
}

/* Foto-uitsnedevenster (bèta JV-17, 27-10-2026): de hulplijnen (stippellijnen, kaderrand, hoeken) van
   Cropper.js waren op een drukke foto nauwelijks te zien. Witte lijnen met een donkere rand eromheen zijn op
   licht én donker beeld zichtbaar (ook voor slechtzienden). */
.cropper-dashed {
    border-color: #ffffff;
    opacity: .9;
    filter: drop-shadow(0 0 1px rgba(0, 0, 0, .9));
}
.cropper-view-box {
    outline: 2px solid #ffffff;
    outline-color: #ffffff;
    box-shadow: 0 0 0 1px rgba(0, 0, 0, .75);
}
.cropper-line,
.cropper-point {
    background-color: #ffffff;
    opacity: .9;
    box-shadow: 0 0 0 1px rgba(0, 0, 0, .75);
}
.cropper-point {
    width: 10px;
    height: 10px;
}
.cropper-center::before,
.cropper-center::after {
    background-color: #ffffff;
    box-shadow: 0 0 0 1px rgba(0, 0, 0, .75);
}

/* Bèta ML-38 (30-10-2026): een niet-aangevinkt vakje had een bijna onzichtbare rand. De rand van een
   keuzevakje en radioknop moet minstens 3:1 contrast hebben met de achtergrond (WCAG 1.4.11);
   --bs-secondary-color (grijs, ca. 4,7:1 op wit) voldoet. Aangevinkte vakjes houden hun vulkleur. */
.form-check-input:not(:checked):not(:disabled) {
    border-color: var(--bs-secondary-color, #6c757d);
    border-width: 2px;
}

/* Algemene zoekbalk bovenaan (partials/topbar, "Zoek in alles waar je bij kunt..."): was alleen zo breed als het standaard
   invoerveld, veel te klein voor een zoekopdracht. Nu neemt hij de beschikbare ruimte links in de topbar in tot max. 640 px,
   en krimpt mee op smallere schermen (onder 768 px staat hij verborgen en is er het zoek-icoon). */
.app-topbar .topbar-menu > .d-flex:first-child {
    flex: 1 1 auto;
    min-width: 0;
}
.app-topbar .app-search {
    flex: 1 1 auto;
    min-width: 160px;
    max-width: 640px;
}
.app-topbar .app-search .form-control {
    width: 100%;
}

/* MYSTIWOT-logo over de volle breedte van het uitgeklapte menu (16-11-2026).
   Het logo schaalt mee met de menubreedte; het icoon-alleen-logo (ingeklapt menu) blijft ongewijzigd. */
.sidenav-menu .logo .logo-lg img {
    height: auto;
    width: calc(100% - 28px);
    max-height: 52px;
    margin: 0 14px;
    object-fit: contain;
    object-position: left center;
}

/* Logo op de inlogschermen (inloggen, code, wachtwoord vergeten/resetten, voorwaarden) groter (16-11-2026). */
.auth-brand .logo-dark img,
.auth-brand .logo-light img {
    height: auto;
    width: 100%;
    max-width: 300px;
    max-height: 80px;
    object-fit: contain;
}

/* Affiliate-overzichten (boeken/dvd's): statuspills iets groter en goed leesbaar. */
.aff-badge {
    font-size: 0.8125rem;
    font-weight: 600;
    padding: 0.4em 0.7em;
}
/* "Niet bestelbaar": donkere tekst op heldere amber, contrast ruim boven 4.5:1 (WCAG AA). */
.aff-badge-unavailable {
    background-color: #ffc107;
    color: #212529;
}
