@charset "UTF-8";
@import url("source-site.css");

/* --- WP-specific additions on top of the site's original stylesheet --- */

/* The original's nav tabs are genuinely two lines of real markup, not a
   word-wrap effect: a light/small "eyebrow" span (.text-field-1--lh-1,
   16px/400) followed by a bold main line inheriting the tab's own
   24px/700 (.title-medium-1--grey) — see the "eyebrow" field built in
   nav-data.php from the menu item's Description.
   The original's tab cluster is also NOT stretched edge-to-edge: its
   `right:0` absolute positioning shrink-wraps to its own content (3 tabs
   at their natural text width, ~250px each) and sits flush against the
   right edge, leaving visible whitespace between it and the logo
   (confirmed via getBoundingClientRect: the tab cluster is 761px wide
   inside a 1180px row, not 1180px). We reproduce that right-aligned-with-
   gap look differently: `.nav-main--menu` (which also contains the
   mega-menu dropdown panels, `.nav-main--sub`) gets `flex-basis: 0` so it
   fills exactly the row's remaining space next to the logo as a definite
   pixel width, NOT a content-based shrink-wrap. Within that now-definite
   width, `.nav-main--menu-desk` naturally fills it as a block flex
   container, and `justify-content: flex-end` right-aligns the actual tabs
   inside it — same visual result (gap on the left, tabs flush right).

   Vertical alignment: the original bottom-aligns the logo and the
   (collapsed) tab row — confirmed live, both end at the same y-coordinate.
   It can do that unconditionally because its logo is `position:fixed`,
   completely immune to how tall anything else on the page is; the tab
   row's own dropdown panels (`.nav-main--sub`) grow in normal flow right
   alongside it without ever touching the logo's position. We don't use
   fixed positioning for the logo (it would need every element below it
   compensated with matching padding, which is its own kind of fragile), so
   a flexbox alignment mode has to stand in for that relationship instead —
   and importantly, it must NOT be `align-items:flex-end`. flex-end
   continuously re-aligns every item in the row to whichever one is
   *currently* tallest; that's fine while collapsed (the logo, at ~136px,
   is taller than the ~76-106px tab row, so tabs correctly sit flush with
   the logo's bottom) but breaks the moment a dropdown opens and
   `.nav-main--menu` becomes the tallest item instead — at that point
   flex-end drags EVERYTHING to align with ITS new bottom edge, and
   whichever fix attempt came before this one just moved the resulting
   jump from the logo onto the tab row or vice versa; the original literally
   cannot have this problem since its logo isn't a flex sibling at all.
   `align-items:flex-start` doesn't have this failure mode: every item's
   TOP always sits at the row's top, in any state, regardless of any
   sibling's height — nothing to ever recalculate when a dropdown opens.
   The trade-off is that flex-start alone top-aligns the logo and tab row
   instead of bottom-aligning them, so nav.js measures both elements' real
   heights once on load and applies a one-time margin-top to
   .nav-main--menu-desk to shift it down into the same bottom-aligned
   position the original has — computed from real DOM measurements, not a
   guessed constant, so it's correct for any admin-entered label length,
   and (unlike align-items) it never gets recalculated by a dropdown
   opening, because the dropdown panels are a separate sibling within
   .nav-main--menu that this margin doesn't apply to. */
@media all and (min-width: 1041px) {
	.limiter.shadow { display: flex; align-items: flex-start; justify-content: space-between; flex-wrap: nowrap; }
	/* The original hardcodes `.header-container{z-index:99}` to float the
	   (position:fixed) logo bar above scrolled page content. Per the
	   Flexbox spec, z-index applies to a flex item even at position:static —
	   so simply by becoming a flex item here (a role it never had in the
	   original, where it isn't a sibling of the nav row at all), that same
	   z-index:99 also stacks it above its flex sibling .nav-main--menu
	   *within this row*, which was never the intent. Confirmed live: this
	   silently hid the thin gray divider line (.nav-main--link:before)
	   wherever it passed under the logo's own box, breaking it into two
	   disconnected segments instead of one continuous line — reset to auto,
	   since nothing here needs the logo stacked above its row sibling. */
	.header-container { width: auto; flex: 0 0 auto; z-index: auto; }
	.nav-main--menu { flex: 1 1 0; min-width: 0; }
	.nav-main--menu-desk { position: static; display: flex; justify-content: flex-end; }
	/* No grow, no cap: each tab sizes to its own text, exactly like the
	   original (confirmed via getBoundingClientRect on the live original:
	   its 3 tabs are 3 different widths — 249px/184px/329px — not a single
	   capped size). A fixed max-width previously forced the longest label
	   ("Über das Med. Zentrallaboratorium") to wrap to a 3rd line, which
	   the original never does — it just gives that tab the room it needs. */
	.nav-main--list { flex: 0 0 auto; }
	.nav-main--link { white-space: normal; }
	/* .nav-main--sub (the dropdown panel) lives inside .nav-main--menu, which
	   only spans the row's remaining space AFTER the logo (1060px of the
	   1180px row, since the logo takes a real 120px flex slot here). The
	   original's dropdown instead spans the FULL 1180px row, starting under
	   the logo itself — confirmed live, its rendered x/width exactly match
	   the header row's, not "row minus logo" — because its logo is
	   position:fixed and doesn't occupy any flex space to begin with, so
	   .nav-main--menu (100% of the row) was never sharing width with it in
	   the first place. Pull the dropdown back out to the left by the logo's
	   own width (a real, fixed, hardcoded design constant — the original's
	   own CSS hardcodes `.header-image{width:120px}` the same way) and widen
	   it to match, so it starts flush with the logo instead of after it. */
	.nav-main--sub { margin-left: -120px; width: calc(100% + 120px); }
}

/* The original header is position:fixed with an absolutely-positioned nav-top
   bar overlapping it (a sticky-header trick tied to their own JS scroll
   listener we didn't reimplement). Simplify to normal in-flow positioning
   so the utility bar renders and stays visible without that extra JS.
   Desktop only (see below for why): on mobile the original's fixed header
   isn't a "trick" needing JS at all — it's unconditionally position:fixed
   (confirmed live: logo, burger AND the red Kontakt/Suche bar all stay
   pinned together while scrolling the reference site's mobile view) — so
   mobile keeps the unmodified source-site.css behaviour below instead of
   this override. */
@media all and (min-width: 1041px) {
	header { position: static !important; }
	/* Thin strip across the full width; the Kontakt/Suche/Home buttons hang
	   below it as a taller red block (same bg colour, so it reads as one bar
	   that's slim everywhere except where the buttons are) - matches the
	   original's `.nav-top-menu{bottom:-30px}` layering, reproduced here with
	   the menu positioned locally within the (now non-fixed) thin bar instead
	   of relative to the whole viewport. */
	.nav-top { position: relative !important; min-height: 8px !important; height: 8px; overflow: visible !important; }
	.nav-top--menu {
		position: absolute !important;
		top: 0;
		right: 0;
		bottom: auto !important;
		display: flex !important;
		align-items: center;
		background-color: #c80000;
		z-index: 20;
	}
	.nav-top--list-last { top: 0 !important; display: flex !important; align-items: center; justify-content: center; }
	/* .wrapper's 125px padding-top exists to clear the original's position:fixed
	   header; since header is static now at this width, that padding is just a
	   dead gap. */
	.wrapper { padding-top: 0 !important; }
}
/* On mobile the original doesn't use its own stylesheet's 125px fallback
   either: it sets #wrapper's padding-top via an inline style (their own JS,
   not reimplemented here — see the main @media block above), to the
   header's REAL rendered height, confirmed live at exactly 97px. That's not
   a measured/variable value on mobile the way the desktop logo/tab
   alignment is (see nav.js) — .header-container and .nav-main are both
   hardcoded `height:97px` in source-site.css itself at this breakpoint, so
   97px is a fixed constant here, not something that needs JS to measure.
   Confirmed live: the source stylesheet's unmodified 125px left a 28px gap
   of blank space between the red bar and the first content below it that
   the reference site doesn't have. */
@media all and (max-width: 1040px) {
	.wrapper { padding-top: 97px !important; }
}
/* The original's mobile menu panel is populated by a SEPARATE, duplicate
   nav list (`.nav-main--list.desk-inactive`, hidden on desktop, shown on
   mobile) — its desktop tab row, `.nav-main--menu-desk`, is unconditionally
   `display:none` below 1041px. This theme has only ONE copy of the nav
   list markup (no duplicate "desk-inactive" items), so un-hide that same
   list on mobile instead of hiding it, rather than reproducing the
   original's two-copies-of-the-same-menu approach. Confirmed live that no
   further markup is needed: `.nav-main--list{width:100%;border:none}` and
   `.nav-main--link{display:block}` are already unconditional (non
   desk-inactive-specific) rules in source-site.css, so the items stack
   full-width automatically once their container is visible. */
@media all and (max-width: 1040px) {
	.nav-main--menu-desk { display: block; position: static; top: auto; right: auto; }
}
/* .nav-main's own padding-top:41px (from source-site.css) is real vertical
   spacing between the thin red top bar and the logo/nav row, not dead space
   left over from the original's position:fixed header trick — confirmed
   live, the original has a genuine ~36px gap there (logo top y=41 vs. top
   bar bottom y=5). A previous round zeroed this out on the wrong assumption
   that it was only there to clear the old fixed positioning; don't override
   it. */

/* The original's mega-menu "slide" open/close is driven by their own JS
   (jQuery slideDown/slideUp) which we didn't reimplement. Replace the plain
   display:none/block toggle with an animated max-height reveal — matching
   the same JS-measured-scrollHeight pattern already used for
   .mzl-accordion-panel (see nav.js), not a guessed fixed cap. A fixed cap
   (this used to be max-height:600px) doesn't just clip content that's
   taller than the guess: transitioning max-height between 0 and a value far
   larger than the real content height is exactly the failure mode Round 9
   already diagnosed for the Kontakt accordion, and it turned out to bite
   here too — confirmed live that the 0 -> 600px transition could get stuck
   at 0 indefinitely (computed max-height never reached 600px even a full
   second after the class toggle; removing the `transition` entirely made it
   resolve instantly and correctly, isolating the transition itself, not the
   cascade, as the cause). JS sets the real max-height inline, so no
   !important is needed here — inline styles already win. */
.nav-main--sub {
	display: block !important;
	max-height: 0;
	padding-top: 0 !important;
	overflow: hidden;
	transition: max-height .35s ease, padding-top .35s ease;
}
/* Desktop only: the dropdown's 75px top padding clears the tab row it
   overlays (see the absolute-positioning comment above). On mobile
   .nav-main--sub is a plain in-flow accordion panel right under the
   clicked item, and source-site.css's own mobile override already zeroes
   this same padding (`.nav-main--sub{padding:0}` at max-width:1040px) —
   confirmed live, leaving this !important unscoped forced 75px of extra
   gap there too, which the reference site doesn't have. nav.js's PANEL_
   PADDING_TOP (the matching JS-side constant) is mobile-aware the same way. */
@media all and (min-width: 1041px) {
	.nav-main--sub.open-desk {
		padding-top: 75px !important;
	}
}

/* The original CMS's rich-text editor (.text-editor) never allowed raw H2/H3/H5/H6
   in body content (only H4, which it styles for indentation only) - its authors
   always used the site's custom title-* classes instead. Since we DO allow real
   heading blocks now, fill that gap with sizes matching the site's existing
   type scale (see .title-medium-3--black and .title-big-2--black for reference). */
.text-editor h2, .editor-styles-wrapper h2 {
	font-family: 'Arial', sans-serif;
	font-size: 24px;
	line-height: 31px;
	font-weight: 700;
	color: rgba(0, 0, 0, 0.9);
	margin: 1.5em 0 .6em;
}
.text-editor h3, .editor-styles-wrapper h3 {
	font-family: 'Arial', sans-serif;
	font-size: 20px;
	line-height: 27px;
	font-weight: 700;
	color: rgba(0, 0, 0, 0.9);
	margin: 1.4em 0 .5em;
}
.text-editor h4, .editor-styles-wrapper h4 {
	font-family: 'Arial', sans-serif;
	font-size: 17px;
	line-height: 24px;
	font-weight: 700;
	color: rgba(0, 0, 0, 0.9);
	margin: 1.2em 0 .5em;
}
.text-editor h5, .text-editor h6, .editor-styles-wrapper h5, .editor-styles-wrapper h6 {
	font-family: 'Arial', sans-serif;
	font-size: 16px;
	font-weight: 700;
	color: rgba(0, 0, 0, 0.9);
	margin: 1em 0 .4em;
}
.text-editor h2:first-child,
.text-editor h3:first-child,
.text-editor h4:first-child,
.editor-styles-wrapper h2:first-child,
.editor-styles-wrapper h3:first-child,
.editor-styles-wrapper h4:first-child { margin-top: 0; }

/* Original site's ul/li had an 80px left indent (via ul padding-left:80px +
   li margin-left:20px + li:before offset -25px) to fit a narrow sidebar-style
   layout. We have full-width space, so drop that indent and give the bullet
   a bit more breathing room from the text instead. */
.text-editor ul, .editor-styles-wrapper ul {
	display: block;
	margin: 20px 0;
	padding-left: 4px;
	list-style: none;
}
.text-editor li, .editor-styles-wrapper li {
	margin-left: 0;
	padding-left: 28px;
	position: relative;
}
.text-editor li:before, .editor-styles-wrapper li:before {
	position: absolute;
	left: 0;
	top: 0;
	content: '•';
	color: #c03;
	margin: 0;
	font-size: 24px;
	line-height: 28px;
}

/* wp:columns block: WP core's own flex layout loads now (see wp-block-styles
   theme support); set our own gap default here to match the rest of the
   site. Deliberately a custom property, not a literal `gap` declaration:
   core's own block CSS is `:where(.is-layout-flex){gap:var(--wp--style--block-gap,2em)}`
   (near-zero specificity via :where(), by design, so themes/blocks can
   always override it) — a literal `.text-editor .wp-block-columns{gap:2rem}`
   here (two real classes) outranks even a block's OWN per-instance
   "Block Spacing" override from the editor (generated as a single-class
   rule, e.g. `.wp-container-core-columns-is-abc123{gap:...}`), which
   silently made that editor control a no-op — confirmed live, setting a
   column's spacing to "None" in the editor had no visible effect. Setting
   the custom property instead doesn't compete with `gap` at all, so it
   only supplies the fallback default and any per-block override still
   wins normally. */
.text-editor .wp-block-columns, .editor-styles-wrapper .wp-block-columns { --wp--style--block-gap: 2rem; margin-bottom: 1.5em; }
.text-editor .wp-block-column img, .editor-styles-wrapper .wp-block-column img { width: 100%; height: auto; }

.screen-reader-text {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip: rect(1px, 1px, 1px, 1px);
	white-space: nowrap;
}

/* Hero rotator */
.header-background--image {
	transition: background-image .6s ease-in-out;
}

/* Content pages rendered through the block editor. max-width matches
   .limiter (the header row's own width: 1180px, centered) so the content
   column starts under the logo and ends under the last nav tab, instead of
   floating narrower and centered within that wider row — the previous
   860px here was our own earlier default, not inherited from the original
   (the original's own `.text-editor{max-width:880px}` doesn't even set
   margin:auto on its own; it was this theme's unrelated 860px rule that
   was centering it). */
.entry-content {
	max-width: 1180px;
	margin: 0 auto;
	padding: 2rem 1rem 4rem;
	overflow: hidden; /* clearfix: contain the floated inline article image */
}
/* The block editor caps each block's own rendered width independently of
   whatever width the real page actually renders at, so paragraphs/columns/
   images wrap and size themselves differently in the editor than they will
   once published. Themes normally fix this by setting
   `--wp--style--global--content-size` (usually via theme.json, which this
   classic theme doesn't have) — but that variable turns out to be a dead
   end here: without theme.json, WordPress's own fallback rule for this is
   `html :where(.wp-block){max-width:840px}`, a LITERAL 840px, not
   `var(--wp--style--global--content-size,840px)` — confirmed live via the
   CSSOM (the variable itself was correctly set to our value, but the block
   still rendered at 840px, because the rule computing its width never
   reads that variable in classic-theme mode). So override the block width
   directly instead — trivial to win since `:where()` carries zero
   specificity by design. 1148px matches .entry-content's real inner
   content width (1180px max-width minus its own 1rem+1rem padding). */
.editor-styles-wrapper .wp-block { max-width: 1148px; }
/* Base text color/size/line-height the published page gets for free from
   the original's own `.text-editor{font-size:16px;line-height:28px;
   color:rgba(0,0,0,0.9)}` (source-site.css) — that rule is scoped to
   `.text-editor`, a class that doesn't exist in the editor's own DOM, so it
   was never reaching plain text there. `.entry-content p` above already
   sets its own more specific line-height (1.6) that wins on the published
   page regardless, so this is really only filling in the base color and
   acting as a fallback line-height for text that isn't inside a <p>. */
.editor-styles-wrapper { font-size: 16px; line-height: 28px; color: rgba(0, 0, 0, 0.9); }
/* source-site.css has a bare `figure{margin:1em 40px}` — from the original
   CMS's lightbox/gallery figures (see the neighbouring `.mfp-figure`,
   `.mfp-img-mobile` rules right next to it — "mfp" = Magnific Popup, their
   lightbox library), never meant for Gutenberg's own `<figure
   class="wp-block-image">` wrapper, which is also a bare <figure> and so
   inherits it by accident. Confirmed live: this 40px left/right margin
   showed up around every image inside a Columns block on the published
   page, but not in the editor (Gutenberg's own block-library CSS happens
   to override the vertical component there, but not the horizontal one —
   hence a lopsided "0px 40px" computed margin). Reset explicitly. */
.entry-content figure.wp-block-image, .editor-styles-wrapper figure.wp-block-image { margin: 0 0 1em; }
.image-container--small { float: left; max-width: 45%; margin: 0 1.5rem 1rem 0; }
.image-container--small img { max-width: 100%; height: auto; }
.image-container--full { width: 100%; margin: 0 0 1.5rem; }
.image-container--full img { width: 100%; height: auto; }
.mzl-standort-address, .mzl-standort-box { clear: both; }
.entry-content h2, .editor-styles-wrapper h2 { margin-top: 2rem; }
.entry-content p, .editor-styles-wrapper p { margin-bottom: 1rem; line-height: 1.6; }
.entry-content ul, .entry-content ol, .editor-styles-wrapper ul, .editor-styles-wrapper ol { margin: 0 0 1rem 1.5rem; }

/* Staff / department listing */
.mzl-staff-group { margin-bottom: 2.5rem; }
.mzl-staff-group h3 { margin-bottom: 1rem; text-transform: uppercase; font-size: .9rem; letter-spacing: .05em; }
.mzl-staff-card { margin-bottom: 1.25rem; }
.mzl-staff-card strong { display: block; }
.mzl-staff-card .role { display: block; opacity: .8; font-size: .9rem; }
.mzl-staff-card a { display: block; font-size: .9rem; }

/* Stat callout table (e.g. Jobs page "160 Mitarbeitende / 10 Millionen Analysen / ...").
   Scoped to .mzl-stat-table specifically so a genuine data table (e.g. the
   Bachelor-/Masterarbeiten list) keeps normal borders/left-aligned text. */
.entry-content figure.mzl-stat-table table, .editor-styles-wrapper figure.mzl-stat-table table { width: 100%; border: none; margin: 2rem 0; }
.entry-content figure.mzl-stat-table td, .editor-styles-wrapper figure.mzl-stat-table td { text-align: center; padding: 1rem; border: none; vertical-align: top; }
.entry-content figure.mzl-stat-table h3, .editor-styles-wrapper figure.mzl-stat-table h3 { font-size: 1.1rem; }
.entry-content figure.mzl-stat-table h3 strong:first-child, .editor-styles-wrapper figure.mzl-stat-table h3 strong:first-child { display: block; font-size: 1.8rem; color: #C80000; }

/* Genuine data tables (native wp:table block) */
.entry-content figure.wp-block-table:not(.mzl-stat-table) table, .editor-styles-wrapper figure.wp-block-table:not(.mzl-stat-table) table { border-collapse: collapse; width: 100%; margin: 1.5rem 0; }
.entry-content figure.wp-block-table:not(.mzl-stat-table) td, .entry-content figure.wp-block-table:not(.mzl-stat-table) th, .editor-styles-wrapper figure.wp-block-table:not(.mzl-stat-table) td, .editor-styles-wrapper figure.wp-block-table:not(.mzl-stat-table) th { border: 1px solid #E5E5E5; padding: .6rem .8rem; text-align: left; vertical-align: top; }
.entry-content figure.wp-block-table:not(.mzl-stat-table) th, .editor-styles-wrapper figure.wp-block-table:not(.mzl-stat-table) th { background: #F7F7F7; }

/* Job listing */
.mzl-job { margin-bottom: 1.5rem; padding-bottom: 1.5rem; border-bottom: 1px solid #e5e5e5; }
.mzl-job h3 { margin-bottom: .5rem; }

/* Download list */
.mzl-downloads { margin: 1.5rem 0; padding: 0; list-style: none; }
.mzl-downloads li { margin-bottom: .5rem; }
.mzl-downloads a { text-decoration: underline; }

/* News */
.mzl-news-item { margin-bottom: 2.5rem; padding-bottom: 2rem; border-bottom: 1px solid #e5e5e5; }
.mzl-news-date { display: block; opacity: .7; font-size: .85rem; margin-bottom: .25rem; }

/* --- Accordion (staff groups, downloads, standort contact box, news items) --- */
.mzl-accordion-toggle {
	display: flex;
	align-items: center;
	justify-content: space-between;
	width: 100%;
	padding: .75rem 1rem;
	background: #F7F7F7;
	border: none;
	border-bottom: 2px solid #C80000;
	font: inherit;
	font-weight: 600;
	text-align: left;
	cursor: pointer;
}
.mzl-accordion-icon { display: inline-block; width: 10px; height: 10px; border-right: 2px solid #C80000; border-bottom: 2px solid #C80000; transform: rotate(45deg); transition: transform .2s ease; flex: none; margin-left: 1rem; }
.mzl-accordion-toggle[aria-expanded="true"] .mzl-accordion-icon { transform: rotate(-135deg); }
/* max-height is set to an exact pixel value by JS (not a large fixed
   number) so the collapse/expand animates smoothly regardless of how
   short or tall the actual content is — see nav.js. */
.mzl-accordion-panel { max-height: 0; overflow: hidden; transition: max-height .25s ease; padding: 0 1rem; }
.mzl-accordion-panel.is-expanded { padding: 1rem; }

/* --- Top utility bar --- */
.mzl-top-bar { background: #C80000; color: #fff; font-size: .8rem; }
.mzl-top-bar .limiter { display: flex; justify-content: flex-end; gap: 1.5rem; padding: .4rem 1rem; }
.mzl-top-bar a { color: #fff; text-decoration: none; }
.mzl-top-bar a:hover { text-decoration: underline; }

/* --- Breadcrumbs --- */
.mzl-breadcrumbs { list-style: none; display: flex; flex-wrap: wrap; gap: .35rem; padding: 1rem; margin: 0; font-size: .8rem; color: #7F7F7F; }
.mzl-breadcrumbs li:not(:last-child)::after { content: '\203A'; margin-left: .35rem; }
.mzl-breadcrumbs a { color: #7F7F7F; text-decoration: none; }
.mzl-breadcrumbs a:hover { color: #C80000; }

/* --- Share button --- */
.mzl-share { padding: 1rem; }
.mzl-share button { background: none; border: 1px solid #ccc; padding: .5rem 1rem; cursor: pointer; font: inherit; }

/* --- Chevron links --- */
.mzl-chevron-link::after { content: '\203A'; color: #C80000; margin-left: .3rem; font-weight: 700; }

/* --- Standort contact panel --- */
.mzl-standort-box { border: 1px solid #E5E5E5; margin: 1.5rem 0; }
.mzl-standort-address { background: #F7F7F7; padding: 1rem; margin-bottom: 1.5rem; }

/* --- Staff cards with photo --- */
.mzl-staff-card { display: flex; gap: 1rem; align-items: flex-start; }
.mzl-staff-card img { width: 72px; height: 72px; object-fit: cover; border-radius: 50%; flex: none; }
.mzl-staff-card-body strong { display: block; }
.mzl-staff-card-body .role { display: block; opacity: .8; font-size: .9rem; }
.mzl-staff-card-body a { display: block; font-size: .9rem; }

/* --- Downloads with icon + filesize --- */
.mzl-downloads { margin: 0; padding: 0; list-style: none; }
.mzl-downloads li { margin-bottom: .6rem; display: flex; align-items: center; gap: .5rem; }
.mzl-downloads .dl-icon { width: 18px; height: 18px; flex: none; }
.mzl-downloads .dl-size { opacity: .6; font-size: .8rem; }

/* --- mzl/pdf-download block: standalone callout box (the existing
   .mzl-job-pdf link this is modelled on has no box styling of its own,
   just an inline icon+text - this needed proper box treatment since it's
   meant to be dropped anywhere in content, not just inside the one
   template that already provides surrounding layout). --- */
.mzl-pdf-callout {
	display: flex;
	align-items: center;
	gap: .6rem;
	margin: 1rem 0;
	padding: .8rem 1rem;
	border: 1px solid #E5E5E5;
	border-left: 3px solid #C80000;
	text-decoration: none;
	color: rgba(0, 0, 0, 0.9);
}
.mzl-pdf-callout:hover { border-color: #C80000; }
.mzl-pdf-callout .dl-icon { width: 20px; height: 20px; flex: none; }
.mzl-pdf-callout-label { font-weight: 700; text-decoration: underline; }
.mzl-pdf-callout .dl-size { opacity: .6; font-size: .85rem; }

/* --- Homepage tile title clamp --- */
.content-link-item-title { display: -webkit-box; -webkit-line-clamp: 2; -webkit-box-orient: vertical; overflow: hidden; }

/* --- Homepage Standorte tiles: share full width regardless of count ---
   source-site.css hardcodes .department-container to width:16.666% (6 tiles).
   Mobile (<768px) keeps the source stacked layout. */
@media all and (min-width: 768px) {
	.mzl-standorte-row { display: flex; }
	.mzl-standorte-row .department-container { flex: 1 1 0; width: auto; min-width: 0; }
}
