/* /Components/Layout/MainLayout.razor.rz.scp.css */
#blazor-error-ui[b-9of0ke0u8w] {
    color-scheme: light only;
    background: lightyellow;
    bottom: 0;
    box-shadow: 0 -1px 2px rgba(0, 0, 0, 0.2);
    box-sizing: border-box;
    display: none;
    left: 0;
    padding: 0.6rem 1.25rem 0.7rem 1.25rem;
    position: fixed;
    width: 100%;
    z-index: 1000;
}

    #blazor-error-ui .dismiss[b-9of0ke0u8w] {
        cursor: pointer;
        position: absolute;
        right: 0.75rem;
        top: 0.5rem;
    }

/* Header: pinned to the top while the page scrolls, so the brand and (on mobile)
   the hamburger button are always reachable. It is a plain block child of <body>
   (NOT a flex item) -- a stretched flex child fills its cell and never sticks.
   z-index keeps it above the content; the opaque background stops content showing
   through as it scrolls underneath. */
.site-header[b-9of0ke0u8w] {
    /* The brand gradient, blue into green -- the strongest, most visible cue that
       carries the school's colours across every page. Built on --color-header, so
       it stays deep in dark mode too (see app.css). No accent underline any more:
       the gradient already ends in green, and the active menu item carries the
       green stroke. */
    background: var(--gradient-brand);
    box-shadow: var(--shadow);
    position: sticky;
    top: 0;
    z-index: 20;
}

.header-inner[b-9of0ke0u8w] {
    max-width: var(--content-width);
    margin: 0 auto;
    padding: var(--space-3) 1.25rem;
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--space-2) var(--space-4);
}

/* Signet and two-line lettering (Brand.razor) side by side. The lettering is sized
   in em, so this font-size is its scale. */
.brand[b-9of0ke0u8w] {
    display: flex;
    align-items: center;
    gap: var(--space-2);
    color: var(--color-on-header);
    text-decoration: none;
    white-space: nowrap;
}

.brand:hover[b-9of0ke0u8w] {
    color: var(--color-on-header);
}

/* On the blue gradient the global brand-blue focus ring would vanish; white
   stays visible on both ends of it. */
.brand:focus-visible[b-9of0ke0u8w] {
    outline-color: var(--color-focus-inverse);
}

/* The signet lives in its own component (Signet.razor), so its <img> carries that
   component's scope attribute, not this one's; ::deep reaches it from here. */
.brand[b-9of0ke0u8w]  .signet {
    flex-shrink: 0;
    width: 3rem;
    height: 3rem;
}

/* The links are pills with their own padding (see app.css), so the gap between
   them can stay small. margin-left:auto pushes the menu to the right edge, away
   from the brand -- the usual split, brand left, menu right. */
.main-nav[b-9of0ke0u8w] {
    margin-left: auto;
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: var(--space-1) var(--space-2);
}

/* The hamburger button and its state checkbox are hidden on wide screens; the
   media query below turns them on for narrow ones. display:none (beating the
   global .visually-hidden the checkbox also carries) takes the checkbox out of the
   tab order here, where there is no menu to open. */
.nav-toggle[b-9of0ke0u8w],
.nav-toggle-label[b-9of0ke0u8w] {
    display: none;
}

/* The link colours/states for .main-nav a live in the GLOBAL app.css, not here.
   Reason: NavLink renders plain <a> elements that carry no scoped-CSS attribute
   (b-xxxxx), so a scoped rule ".main-nav a" would not match them. See app.css. */

/* Content: at least tall enough that the footer sits at the bottom of the viewport
   on short pages. 100dvh - 5rem leaves room for the header with its signet (which
   sits above in normal flow); dvh follows the mobile browser's shrinking toolbar.
   On long pages the content simply grows past this and pushes the footer down
   naturally. */
.content[b-9of0ke0u8w] {
    min-height: calc(100dvh - 5rem);
    box-sizing: border-box;
    width: 100%;
    max-width: var(--content-width);
    margin: 0 auto;
    padding: var(--space-4) 1.25rem var(--space-6);
}

/* Footer: a dark brand-blue band with light text, so the page visibly ends here.
   Its own tokens (--color-footer, --color-on-footer...) keep it dark in both
   colour schemes, like the header. position:relative anchors the wave. */
.site-footer[b-9of0ke0u8w] {
    position: relative;
    margin-top: var(--space-6);
    background: var(--color-footer);
    color: var(--color-on-footer-soft);
    font-size: 0.95rem;
}

/* The wave sits just above the footer's top edge (bottom: 100%), drawn over the
   page background in the footer colour, so the band seems to rise softly instead
   of starting with a hard line. Fixed height, full width: on a phone it simply
   flattens out. Overlapped by 1px so no hairline gap shows between wave and band
   when the browser rounds. */
.footer-wave[b-9of0ke0u8w] {
    position: absolute;
    bottom: calc(100% - 1px);
    left: 0;
    display: block;
    width: 100%;
    height: 2.5rem;
    fill: var(--color-footer);
}

/* Three columns: brand, quick links, further pages. The brand gets a bit more room
   because it holds the signet. A missing link column simply leaves its cell empty,
   so the others keep their place. */
.footer-inner[b-9of0ke0u8w] {
    max-width: var(--content-width);
    margin: 0 auto;
    padding: var(--space-5) 1.25rem var(--space-4);
    display: grid;
    grid-template-columns: 1.5fr 1fr 1fr;
    gap: var(--space-4);
}

/* The same mark as in the header, a little smaller: the footer closes the page, it
   does not introduce it. */
.footer-brand[b-9of0ke0u8w] {
    display: flex;
    align-items: center;
    align-self: start;
    gap: var(--space-2);
    color: var(--color-on-footer);
    font-size: 0.9rem;
}

.footer-brand[b-9of0ke0u8w]  .signet {
    flex-shrink: 0;
    width: 2.75rem;
    height: 2.75rem;
}

/* Column headings label the lists; they are not a second page heading, so they
   stay small and quiet. */
.footer-heading[b-9of0ke0u8w] {
    margin: 0 0 var(--space-2);
    color: var(--color-on-footer);
    font-size: 0.8rem;
    font-weight: 700;
    letter-spacing: 0.08em;
    text-transform: uppercase;
}

.footer-nav ul[b-9of0ke0u8w] {
    list-style: none;
    margin: 0;
    padding: 0;
}

.footer-nav li + li[b-9of0ke0u8w] {
    margin-top: var(--space-1);
}

.footer-nav a[b-9of0ke0u8w] {
    color: var(--color-on-footer-soft);
    text-decoration: none;
}

.footer-nav a:hover[b-9of0ke0u8w] {
    color: var(--color-on-footer);
    text-decoration: underline;
}

/* Same reason as the brand link in the header: a light ring on the dark band. */
.footer-nav a:focus-visible[b-9of0ke0u8w] {
    outline-color: var(--color-focus-inverse);
}

/* Copyright: a thin rule separates it from the columns. The rule spans the content
   width, not the whole window, so it lines up with the columns above. */
.footer-copyright[b-9of0ke0u8w] {
    box-sizing: border-box;
    max-width: var(--content-width);
    margin: 0 auto;
    padding: var(--space-3) 1.25rem;
    border-top: 1px solid var(--color-footer-border);
    font-size: 0.85rem;
}

/* Narrow screens: the nav collapses behind a hamburger button. This is pure CSS --
   the #nav-toggle checkbox holds the open/closed state and its :checked state
   reveals the nav. No JavaScript, so it works under static SSR. Without JavaScript
   the header cannot measure whether the links still fit, so the switch happens at a
   fixed width instead: brand plus the current menu need about 1000 px. When the
   menu in PocketBase gets longer and the links start to wrap, raise this value
   (and the matching one in app.css). */
@media (max-width: 64rem) {
    /* The brand stays on the left, the hamburger goes to the right, and the nav
       occupies its own full-width row below both. */
    .header-inner[b-9of0ke0u8w] {
        flex-wrap: wrap;
        align-items: center;
        justify-content: space-between;
        /* No row gap: the folded nav is a zero-height second row, and a gap above
           it would leave empty space under the brand, pushing it off centre. The
           open nav brings its own distance instead (margin-top below). */
        row-gap: 0;
    }

    /* The checkbox comes back as a real, focusable control -- only visually hidden
       (global .visually-hidden), so Tab stops on it and Space toggles the menu. It
       lives under the label, so the focus ring is drawn there instead. */
    .nav-toggle[b-9of0ke0u8w] {
        display: block;
    }

    .nav-toggle:focus-visible + .nav-toggle-label[b-9of0ke0u8w] {
        outline: 3px solid var(--color-focus-inverse);
        outline-offset: 2px;
        border-radius: var(--radius);
    }

    /* Show the hamburger button. */
    .nav-toggle-label[b-9of0ke0u8w] {
        display: block;
        cursor: pointer;
        padding: 0.5rem;
        margin: -0.5rem;   /* keep the tap target large without shifting layout */
    }

    /* The three-bar icon, drawn with one element plus its ::before/::after. */
    .nav-toggle-bar[b-9of0ke0u8w],
    .nav-toggle-bar[b-9of0ke0u8w]::before,
    .nav-toggle-bar[b-9of0ke0u8w]::after {
        display: block;
        width: 1.5rem;
        height: 2px;
        background: var(--color-on-header);
        content: "";
        transition: transform var(--transition), background-color var(--transition);
    }

    .nav-toggle-bar[b-9of0ke0u8w]::before {
        transform: translateY(-6px);
    }

    .nav-toggle-bar[b-9of0ke0u8w]::after {
        transform: translateY(4px);   /* 6px minus the bar's own 2px height */
    }

    /* Open: the hamburger turns into an X. The middle bar fades out and the outer
       two meet in the middle and cross. Only the icon changes shape; nothing around
       it moves. The checkbox sits right before the label, hence the + combinator. */
    .nav-toggle:checked + .nav-toggle-label .nav-toggle-bar[b-9of0ke0u8w] {
        background-color: transparent;
    }

    .nav-toggle:checked + .nav-toggle-label .nav-toggle-bar[b-9of0ke0u8w]::before {
        transform: rotate(45deg);
    }

    .nav-toggle:checked + .nav-toggle-label .nav-toggle-bar[b-9of0ke0u8w]::after {
        transform: translateY(-2px) rotate(-45deg);   /* back up by its own height */
    }

    /* The nav takes its own row and is hidden until the checkbox is checked.
       max-height:0 alone would only hide it from the eye: its links would still
       be Tab stops and still be read out. visibility:hidden takes them out of
       both. Transitioning visibility delays the switch to hidden until the fold
       has finished, so closing still animates. Opening uses the transition of the
       :checked rule below, which leaves visibility out: the links must be Tab
       stops the moment Space is pressed, not 0.2s later. */
    .main-nav[b-9of0ke0u8w] {
        flex-basis: 100%;
        flex-direction: column;
        gap: 0;
        max-height: 0;
        overflow: hidden;
        visibility: hidden;
        transition: max-height 0.2s ease, visibility 0.2s;
    }

    /* Checked state: reveal the stacked links. The max-height caps the open menu
       to the space below the sticky header; a longer list scrolls inside it
       instead of running off the screen. */
    .nav-toggle:checked ~ .main-nav[b-9of0ke0u8w] {
        visibility: visible;
        transition: max-height 0.2s ease;
        max-height: 70vh;
        overflow-y: auto;
        margin-top: var(--space-3);
    }

    /* Mobile per-link spacing for .main-nav a is in the global app.css too, for
       the same scoped-attribute reason as above. */
}

/* Phones. */
@media (max-width: 40rem) {
    /* The header stays pinned while scrolling, so on a small screen every pixel of
       its height is lost for content. Less padding, a smaller signet and lettering
       bring it down to about 56 px, the usual height of a phone's top bar. */
    .header-inner[b-9of0ke0u8w] {
        padding-block: var(--space-2);
    }

    .brand[b-9of0ke0u8w]  .signet {
        width: 2.5rem;
        height: 2.5rem;
    }

    .brand[b-9of0ke0u8w] {
        font-size: 0.86rem;
    }

    /* The footer columns stack: one column, brand on top. */
    .footer-inner[b-9of0ke0u8w] {
        grid-template-columns: 1fr;
    }
}
/* /Features/Embeds/DocumentsEmbed.razor.rz.scp.css */
/* The cards come from the global app.css (the lone PDF link). Unlike the post and
   event teasers, the list belongs to the page's reading column, so it takes the same
   centred 42rem as ContentPage's text, whose scoped rule does not reach in here. */
.embed-documents[b-5bqi3nv28j] {
    max-width: 42rem;
    margin-inline: auto;
    margin-top: var(--space-5);
}
/* /Features/Embeds/EventsEmbed.razor.rz.scp.css */
/* The card is EventCard and the list grid lives in the global app.css, shared with
   the full events page. Only the embed's spacing on the home page is specific here. */
.embed-events[b-o4j9jiq3an] {
    margin-top: var(--space-5);
}
/* /Features/Embeds/PostsEmbed.razor.rz.scp.css */
/* The card is PostCard and the list grid lives in the global app.css, shared with
   the full posts page. Only the embed's spacing on the home page is specific here. */
.embed-posts[b-wux6h7htit] {
    margin-top: var(--space-5);
}
/* /Features/Events/CalendarSheet.razor.rz.scp.css */
/* The calendar sheet: a green band with the month over a large day number and the
   weekday. Fixed width, so the sheets of a list line up whatever the month. The band
   has its own token (--color-calendar-band): the plain green accent is too light for
   small white text, the band's darker green keeps it above AA in both schemes.
   Positioning (gap to the text beside it) is the caller's job. */
.calendar-sheet[b-tqpwj64xvp] {
    flex-shrink: 0;
    display: flex;
    flex-direction: column;
    width: 4rem;
    overflow: hidden;
    border: 1px solid var(--color-border);
    border-radius: var(--radius-sm);
    background: var(--color-bg);
    text-align: center;
    line-height: 1.2;
}

.calendar-month[b-tqpwj64xvp] {
    padding: 0.15rem 0;
    background: var(--color-calendar-band);
    color: var(--color-on-button);
    font-size: 0.8rem;
    font-weight: 700;
    letter-spacing: 0.05em;
    text-transform: uppercase;
}

.calendar-day[b-tqpwj64xvp] {
    padding-top: var(--space-1);
    color: var(--color-heading);
    font-size: 1.75rem;
    font-weight: var(--font-weight-heading);
}

.calendar-weekday[b-tqpwj64xvp] {
    padding-bottom: var(--space-1);
    color: var(--color-text-soft);
    font-size: 0.8rem;
    font-weight: 600;
}
/* /Features/Events/EventCard.razor.rz.scp.css */
/* The event card: a white surface on the tinted page, sheet left, text right. The
   card fills its list cell, so the cards of a row are equally tall. */
.event-card[b-bmt0jj0zg3] {
    box-sizing: border-box;
    display: flex;
    gap: var(--space-3);
    align-items: flex-start;
    height: 100%;
    padding: var(--space-3) var(--space-4);
    border: 1px solid transparent;
    border-radius: var(--radius);
    background: var(--color-bg);
    box-shadow: var(--shadow);
    color: var(--color-text);
}

/* Only the linked card reacts to hover: a card that leads nowhere must not look
   clickable. Hover = stronger shadow and a blue edge, nothing moves. */
.event-card-link[b-bmt0jj0zg3] {
    text-decoration: none;
    transition: box-shadow var(--transition), border-color var(--transition);
}

.event-card-link:hover[b-bmt0jj0zg3] {
    border-color: var(--color-brand);
    box-shadow: var(--shadow-hover);
    color: var(--color-text);
}

.event-details[b-bmt0jj0zg3] {
    display: flex;
    flex-direction: column;
    gap: var(--space-1);
    min-width: 0;   /* lets a long title wrap instead of widening the card */
}

.event-title[b-bmt0jj0zg3] {
    color: var(--color-brand);
    font-size: 1.15rem;
    font-weight: 700;
    line-height: 1.3;
}

/* Time and place: icon and text on one quiet line each. The icon belongs to Icon's
   own scope, so it is reached through ::deep. */
.event-meta[b-bmt0jj0zg3] {
    display: flex;
    align-items: center;
    gap: var(--space-1);
    color: var(--color-text-soft);
    font-size: 0.9rem;
}

.event-meta[b-bmt0jj0zg3]  .icon {
    color: var(--color-accent-dark);
}

/* pre-line keeps the editor's line breaks from the plain-text note field. */
.event-note[b-bmt0jj0zg3] {
    margin-top: var(--space-1);
    font-size: 0.95rem;
    white-space: pre-line;
}

/* In the linked card (home embed) the note is only a teaser: cut after two lines,
   so a long note does not stretch the card next to short ones. The full note is
   on the events page. */
.event-card-link .event-note[b-bmt0jj0zg3] {
    display: -webkit-box;
    -webkit-box-orient: vertical;
    -webkit-line-clamp: 2;
    line-clamp: 2;
    overflow: hidden;
}

.event-ics[b-bmt0jj0zg3] {
    display: inline-flex;
    align-items: center;
    gap: var(--space-1);
    align-self: flex-start;
    margin-top: var(--space-2);
    font-size: 0.9rem;
    font-weight: 600;
}
/* /Features/Events/EventDate.razor.rz.scp.css */
/* The date's own look: small and softened, matching <PostDate> so post and event
   cards read as one style. Lives with the component so every place that renders
   <EventDate> (list, home embed) shows the date the same way. Positioning (margin
   to neighbours) is NOT set here -- that is the surrounding list's job. */
time[b-k34xjycpot] {
    display: block;
    color: var(--color-text-soft);   /* token, so it adapts in dark mode */
    font-size: 0.85rem;
}
/* /Features/Events/EventList.razor.rz.scp.css */
/* The card grid (.event-list) is shared with the home-page embed and lives in the
   global app.css; the card itself is EventCard. Only the page's own parts are here. */

/* Same centred 42rem reading column as a content page (ContentPage.razor.css), so
   every page of the site shares one column under the header. */
h1[b-0kf4adcxxy],
h2[b-0kf4adcxxy],
article[b-0kf4adcxxy],
p[b-0kf4adcxxy],
.event-list[b-0kf4adcxxy],
.past-events[b-0kf4adcxxy] {
    max-width: 42rem;
    margin-inline: auto;
}

/* auto, not 0: this rule outweighs the column rule above and would otherwise pull
   the button back to the left edge of the page. */
.events-subscribe[b-0kf4adcxxy] {
    margin: var(--space-4) auto;
}

/* Past events: one folded-up card. Opened, a compact list grouped by year,
   deliberately quieter than the upcoming cards above. The open/close triangle is
   the shared .disclosure rule in app.css, the same as on the FAQ topics. */
.past-events[b-0kf4adcxxy] {
    box-sizing: border-box;   /* padding inside the 42rem, flush with the text */
    margin-top: var(--space-5);
    padding: var(--space-3) var(--space-4);
    border: 1px solid var(--color-border);
    border-radius: var(--radius);
    background: var(--color-surface);
}

.past-events-year[b-0kf4adcxxy] {
    margin: var(--space-4) 0 var(--space-1);
    color: var(--color-text-soft);
    font-size: 0.9rem;
    font-weight: 700;
    letter-spacing: 0.04em;
}

.past-events ul[b-0kf4adcxxy] {
    margin: 0;
    padding: 0;
    list-style: none;
}

/* On a phone the day sits above the title: a column beside it would leave the
   title too little room. */
.past-events li[b-0kf4adcxxy] {
    display: grid;
    padding: var(--space-2) 0;
    border-top: 1px solid var(--color-border);
}

/* From tablet width on, day and title side by side. The day column has a fixed
   width, so every title starts on the same line; it fits the longest single day,
   "30. September". A span across months ("30. Januar – 2. Februar") wraps after
   the dash inside the column. Same font size for both and baseline alignment, so
   the two texts sit on one line. */
@media (min-width: 40rem) {
    .past-events li[b-0kf4adcxxy] {
        grid-template-columns: 8rem 1fr;
        column-gap: var(--space-3);
        align-items: baseline;
    }
}

/* Tabular digits give every day the same width, so "1." and "10." line up. */
.past-event-date[b-0kf4adcxxy] {
    color: var(--color-text-soft);
    font-variant-numeric: tabular-nums;
}

.past-event-title[b-0kf4adcxxy] {
    color: var(--color-text);
}

/* The time trails the title, quieter, as an addition rather than part of the name. */
.past-event-time[b-0kf4adcxxy] {
    margin-left: var(--space-2);
    color: var(--color-text-soft);
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}
/* /Features/Faqs/FaqList.razor.rz.scp.css */
/* Same centred 42rem reading column as a content page (ContentPage.razor.css), so
   every page of the site shares one column under the header. The topic cards and
   the questions inside them live in the global app.css. */
h1[b-ly0rwws06f],
article[b-ly0rwws06f],
p[b-ly0rwws06f],
.faq-topic[b-ly0rwws06f] {
    box-sizing: border-box;   /* padding inside the 42rem, flush with the text */
    max-width: 42rem;
    margin-inline: auto;
}

/* The intro's last paragraph drops its margin (app.css), so the first card would
   sit right under the text; this gives it the same air as between sections. */
article[b-ly0rwws06f] {
    margin-bottom: var(--space-5);
}
/* /Features/Home/Home.razor.rz.scp.css */
/* --- Hero ---------------------------------------------------------------------
   A full-width band in the brand gradient with a faint dot pattern on top. The
   page content sits in a centred column (.content in MainLayout), so the band
   breaks out of it: 100vw wide, pulled left by the column's offset. body clips the
   few pixels of scrollbar this adds (see app.css). The negative top margin cancels
   the column's top padding, so the band meets the header without a strip of page
   background in between.
   The pattern is an inline SVG in a data: URL -- no request, nothing from another
   host. White dots at 12% opacity: visible as texture, too faint to cost the
   white text any contrast. */
.hero[b-rfcyvv48s0] {
    width: 100vw;
    margin: calc(-1 * var(--space-4)) 0 var(--space-5) calc(50% - 50vw);
    background:
        url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24'%3E%3Ccircle cx='3' cy='3' r='1.5' fill='%23fff' fill-opacity='.12'/%3E%3C/svg%3E"),
        var(--gradient-brand);
    color: var(--color-on-header);
}

/* The inside follows the page frame again, so the hero text lines up with the
   tiles and lists below. Stacked on a phone; from tablet width the next-event card
   moves beside the text. */
.hero-inner[b-rfcyvv48s0] {
    box-sizing: border-box;
    max-width: var(--content-width);
    margin: 0 auto;
    padding: var(--space-6) 1.25rem;
    display: grid;
    gap: var(--space-5);
    align-items: center;
}

@media (min-width: 48rem) {
    .hero-inner[b-rfcyvv48s0] {
        grid-template-columns: minmax(0, 1fr) minmax(16rem, 22rem);
    }
}

/* On the gradient everything is white: the global heading colour is a blue that
   would vanish here. */
/* balance evens out the lines, so a short last word ("IGMH") never wraps alone. */
.hero h1[b-rfcyvv48s0] {
    color: var(--color-on-header);
    text-wrap: balance;
}

/* The intro is editor Markdown, rendered without scope attributes, so it is reached
   through ::deep. Slightly larger than body text, as a lead. Links stay white and
   underlined: the blue link colour would be unreadable on the gradient. */
.hero-intro[b-rfcyvv48s0]  p {
    font-size: 1.15rem;
}

.hero-intro[b-rfcyvv48s0]  a,
.hero-intro[b-rfcyvv48s0]  a:hover {
    color: var(--color-on-header);
}

.hero-actions[b-rfcyvv48s0] {
    display: flex;
    flex-wrap: wrap;
    gap: var(--space-3);
    margin: var(--space-4) 0 0;
}

/* The hero's buttons, adapted to the dark gradient: the primary turns light (a
   filled blue would melt into the blue end), the secondary becomes a white outline
   with the same translucent wash as the header menu on hover. The focus ring turns
   white for the same reason. */
.hero .btn-primary[b-rfcyvv48s0] {
    background: var(--color-button-light);
    border-color: var(--color-button-light);
    color: var(--color-on-button-light);
}

.hero .btn-primary:hover[b-rfcyvv48s0] {
    background: var(--color-button-light-hover);
    border-color: var(--color-button-light-hover);
    color: var(--color-on-button-light);
}

.hero .btn-secondary[b-rfcyvv48s0] {
    border-color: var(--color-on-header);
    color: var(--color-on-header);
}

.hero .btn-secondary:hover[b-rfcyvv48s0] {
    background: var(--color-nav-hover);
    color: var(--color-on-header);
}

.hero .btn:focus-visible[b-rfcyvv48s0] {
    outline-color: var(--color-focus-inverse);
}

/* On a phone the buttons used to wrap onto a row each: two wide blocks stacked,
   far too heavy for the top of the page. Instead they share one row in equal
   columns -- the same buttons as on the desktop, just side by side and a little
   tighter. Short labels ("Termine", "Kontakt") fit on one line; a longer one
   wraps inside its button (centred) rather than pushing the other off the row. */
@media (max-width: 40rem) {
    .hero-actions[b-rfcyvv48s0] {
        display: grid;
        grid-auto-flow: column;
        grid-auto-columns: 1fr;
        gap: var(--space-2);
    }

    .hero .btn[b-rfcyvv48s0] {
        justify-content: center;
        padding: var(--space-2) var(--space-3);
        text-align: center;
    }
}

/* --- Next event ---------------------------------------------------------------
   A card on the gradient: the regular card surface, so its text uses the normal
   tokens and adapts to dark mode by itself. The whole card is one link to the
   events page. */
.next-event[b-rfcyvv48s0] {
    display: block;
    padding: var(--space-4);
    border-radius: var(--radius);
    background: var(--color-bg);
    box-shadow: var(--shadow-lg);
    color: var(--color-text);
    text-decoration: none;
    transition: box-shadow var(--transition);
}

.next-event:hover[b-rfcyvv48s0] {
    color: var(--color-text);
    box-shadow: var(--shadow-hover), var(--shadow-lg);
}

/* The ring sits outside the card, on the gradient, so it is white like the
   hero's button rings. */
.next-event:focus-visible[b-rfcyvv48s0] {
    outline-color: var(--color-focus-inverse);
    outline-offset: 3px;
}

.next-event-label[b-rfcyvv48s0] {
    display: block;
    margin-bottom: var(--space-3);
    color: var(--color-text-soft);
    font-size: 0.85rem;
    font-weight: 700;
    letter-spacing: 0.05em;
    text-transform: uppercase;
}

.next-event-row[b-rfcyvv48s0] {
    display: flex;
    gap: var(--space-3);
    align-items: flex-start;
}

.next-event-details[b-rfcyvv48s0] {
    min-width: 0;   /* lets a long title wrap instead of widening the card */
}

.next-event-title[b-rfcyvv48s0] {
    display: block;
    color: var(--color-brand);
    font-size: 1.15rem;
    font-weight: 700;
    line-height: 1.3;
}

/* Time and place, one line each with their icon, green as on the event cards. The
   icon belongs to Icon's own scope, so it is reached through ::deep. */
.next-event-meta[b-rfcyvv48s0] {
    display: flex;
    align-items: center;
    gap: var(--space-1);
    margin-top: var(--space-1);
    color: var(--color-text-soft);
    font-size: 0.9rem;
}

.next-event-meta[b-rfcyvv48s0]  .icon {
    color: var(--color-accent-dark);
}

/* --- Tiles --------------------------------------------------------------------
   One card per header page. Fixed columns instead of auto-fill: two on a phone,
   three from tablet width, so the six pages always fill whole rows and never leave
   a half row behind. On a phone the tiles are compact (icon and title only), the
   teaser would make six tiles a long scroll. Hover = stronger shadow and a blue
   edge, nothing moves. */
.home-tiles[b-rfcyvv48s0] {
    margin-block: var(--space-5);
}

.home-tiles ul[b-rfcyvv48s0] {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: var(--space-3);
    margin: 0;
    padding: 0;
    list-style: none;
}

/* On a phone the icon sits above the title: beside it, a half-width column leaves
   too little room and titles get cut. */
.tile-link[b-rfcyvv48s0] {
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    align-items: center;
    gap: var(--space-2);
    height: 100%;
    text-align: center;
    padding: var(--space-3);
    border: 1px solid transparent;
    border-radius: var(--radius);
    background: var(--color-bg);
    box-shadow: var(--shadow);
    color: var(--color-text);
    text-decoration: none;
    transition: box-shadow var(--transition), border-color var(--transition);
}

.tile-link:hover[b-rfcyvv48s0] {
    border-color: var(--color-brand);
    box-shadow: var(--shadow-hover);
    color: var(--color-text);
}

/* The icon in a soft round tint. */
.tile-icon[b-rfcyvv48s0] {
    flex-shrink: 0;
    display: grid;
    place-items: center;
    width: 3rem;
    height: 3rem;
    border-radius: 50%;
    background: var(--color-brand-tint);
    color: var(--color-brand);
}

/* Long German compounds must wrap rather than overflow the narrow tile. */
.tile-title[b-rfcyvv48s0] {
    max-width: 100%;
    color: var(--color-brand);
    font-size: 1.1rem;
    font-weight: 700;
    overflow-wrap: anywhere;
}

/* Hidden on a phone; the title alone says where the tile leads. */
.tile-text[b-rfcyvv48s0] {
    display: none;
    color: var(--color-text-soft);
    font-size: 0.9rem;
    line-height: 1.45;
}

@media (min-width: 48rem) {
    .home-tiles ul[b-rfcyvv48s0] {
        grid-template-columns: repeat(3, minmax(0, 1fr));
    }

    /* Icon left, title and teaser right. Both start at the top, so the icon stays
       beside the title even when the teaser runs over several lines. The icon spans
       both rows here, where the teaser is visible. */
    .tile-link[b-rfcyvv48s0] {
        display: grid;
        grid-template-columns: auto minmax(0, 1fr);
        column-gap: var(--space-3);
        row-gap: 0;
        align-content: start;
        padding: var(--space-3) var(--space-4);
        text-align: start;
    }

    .tile-icon[b-rfcyvv48s0] {
        grid-row: span 2;
        align-self: start;
    }

    /* The teaser is a whole sentence; the tile cuts it visually after three lines,
       so the tiles of a row keep a similar height whatever the editor wrote. The
       -webkit- box is the form every current browser supports for line-clamp. */
    .tile-text[b-rfcyvv48s0] {
        display: -webkit-box;
        -webkit-box-orient: vertical;
        -webkit-line-clamp: 3;
        line-clamp: 3;
        overflow: hidden;
    }
}

/* --- Embeds -------------------------------------------------------------------
   The blocks the home page opts into (posts, events) sit side by side from desktop
   width, so the start page shows both without a long scroll. One column below.
   In the grid the blocks' own top margin no longer collapses with the margin of
   the tiles above, so it is dropped there; otherwise the gap would be doubled. */
@media (min-width: 64rem) {
    .home-embeds[b-rfcyvv48s0] {
        display: grid;
        grid-template-columns: repeat(2, minmax(0, 1fr));
        gap: var(--space-5);
        align-items: start;
    }

    .home-embeds[b-rfcyvv48s0]  .embed {
        margin-top: 0;
    }
}
/* /Features/Layout/Brand.razor.rz.scp.css */
/* The name and the school line up on the left edge as a column of their own. Sizes in
   em, so the parent sets the scale with one font-size: full size in the header,
   smaller on phones and in the footer. */
.brand-text[b-uqca9kyim0] {
    display: flex;
    flex-direction: column;
    line-height: 1.15;
}

.brand-name[b-uqca9kyim0] {
    font-size: 1.35em;
    font-weight: var(--font-weight-heading);
    letter-spacing: var(--letter-spacing-heading);
}

.brand-school[b-uqca9kyim0] {
    font-size: 0.85em;
    font-weight: 600;
}
/* /Features/Layout/Signet.razor.rz.scp.css */
/* The image is already white on transparent; it only needs to behave as a block so
   no inline gap appears below it. */
.signet[b-a980yt1vd8] {
    display: block;
}
/* /Features/Pages/ContentPage.razor.rz.scp.css */
/* A content page is one reading column: its text, boxes and card grids all stop at
   42rem (app.css). Left-aligned in the 72rem layout that column left a wide empty
   strip on the right of a desktop screen; centred, the empty space splits evenly and
   the page sits balanced under the header. Title and body share the column, so they
   keep one left edge. The children inside keep margin 0 and simply fill it. */
h1[b-aeibmpeeou],
article[b-aeibmpeeou],
p[b-aeibmpeeou] {
    max-width: 42rem;
    margin-inline: auto;
}
/* /Features/Posts/PostCard.razor.rz.scp.css */
/* The post card: a white surface with a green stripe on the left as the eye's
   anchor. The stripe is a border, so it follows the rounded corners. The whole card
   is the link and fills its list cell, so the cards of a row are equally tall.
   Hover = stronger shadow, nothing moves. */
.post-card[b-cjrzhuw1bk] {
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    gap: var(--space-2);
    height: 100%;
    padding: var(--space-3) var(--space-4);
    border-left: 4px solid var(--color-accent);
    border-radius: var(--radius);
    background: var(--color-bg);
    box-shadow: var(--shadow);
    color: var(--color-text);
    text-decoration: none;
    transition: box-shadow var(--transition);
}

.post-card:hover[b-cjrzhuw1bk] {
    box-shadow: var(--shadow-hover);
    color: var(--color-text);
}

/* Icon and date on one line. The icon belongs to Icon's own scope, so it is
   reached through ::deep. */
.post-date[b-cjrzhuw1bk] {
    display: flex;
    align-items: center;
    gap: var(--space-1);
}

.post-date[b-cjrzhuw1bk]  .icon {
    color: var(--color-accent-dark);
}

.post-title[b-cjrzhuw1bk] {
    color: var(--color-brand);
    font-size: 1.15rem;
    font-weight: 700;
    line-height: 1.3;
}

/* Cut after three lines, so cards of a row stay close in height whatever the
   editor wrote. The featured card lifts the limit (see below). */
.post-teaser[b-cjrzhuw1bk] {
    display: -webkit-box;
    -webkit-box-orient: vertical;
    -webkit-line-clamp: 3;
    line-clamp: 3;
    overflow: hidden;
    font-size: 0.95rem;
}

/* margin-top: auto pushes the link line to the bottom, so it sits on one level
   across a row of cards with teasers of different length. */
.post-more[b-cjrzhuw1bk] {
    display: inline-flex;
    align-items: center;
    gap: var(--space-1);
    margin-top: auto;
    padding-top: var(--space-1);
    color: var(--color-brand);
    font-size: 0.9rem;
    font-weight: 700;
}

/* The newest post on the posts page: more room, a larger title and the full
   teaser. */
.post-card-featured[b-cjrzhuw1bk] {
    padding: var(--space-4) var(--space-5);
}

.post-card-featured .post-title[b-cjrzhuw1bk] {
    font-size: var(--font-size-h3);
}

@media (min-width: 48rem) {
    .post-card-featured .post-title[b-cjrzhuw1bk] {
        font-size: 1.5rem;
    }
}

.post-card-featured .post-teaser[b-cjrzhuw1bk] {
    display: block;
    font-size: 1rem;
}
/* /Features/Posts/PostDate.razor.rz.scp.css */
/* The date's own look: small and softened. Lives with the component so every
   place that renders <PostDate> (list, home embed, detail page) shows the date
   the same way. Positioning (margin to neighbours) is NOT set here -- that
   depends on the surrounding context and is set by each caller. */
time[b-su57q8a33n] {
    display: block;
    color: var(--color-text-soft);   /* token, so it adapts in dark mode */
    font-size: 0.85rem;
}
/* /Features/Posts/PostDetail.razor.rz.scp.css */
/* The article: the site's centred 42rem reading column (as on a content page,
   ContentPage.razor.css) with generous leading, so a long post reads like a page,
   not like a form. Everything inside follows this width -- the global 42rem cap on
   paragraphs, lists and boxes is lifted here, so nothing stops short of the column
   (the post's own leading makes the text a touch wider than elsewhere). */
.post[b-qxq77a12os] {
    max-width: 42rem;
    margin: var(--space-4) auto 0;
    line-height: 1.75;
}

/* The back link is an inline button, which margin: auto cannot centre. A left
   margin of half the free space puts it on the column's left edge instead, and
   max() keeps it at 0 once the screen is narrower than the column. */
.btn-quiet[b-qxq77a12os] {
    margin-left: max(0px, (100% - 42rem) / 2);
}

.post[b-qxq77a12os]  :is(p, ul, ol, blockquote, .aufruf, .hinweis) {
    max-width: none;
}

/* Date above the title as a quiet meta line, with the same calendar icon as on the
   post cards. The title follows directly, so the gap between them stays small
   (h1 carries no top margin globally). */
.post-meta[b-qxq77a12os] {
    display: flex;
    align-items: center;
    gap: var(--space-1);
    margin: 0 0 var(--space-2);
    color: var(--color-text-soft);
    font-size: 0.95rem;
    font-weight: 600;
}

.post-meta[b-qxq77a12os]  .icon {
    color: var(--color-accent-dark);
}

/* The first paragraph as the lead: larger and in the soft tone, so it reads as an
   introduction. Pure CSS on the editor's Markdown -- if a post starts with a
   heading or a list instead, there simply is no lead. Same text colour token as
   the rest, so it keeps AA contrast in both schemes. */
.post-body[b-qxq77a12os]  > p:first-child {
    color: var(--color-text-soft);
    font-size: 1.2rem;
    line-height: 1.65;
}

/* Older/newer post at the end: two cards side by side, older on the left, newer on
   the right. The grid keeps each in its column even if the other is missing. Hover
   = border and shadow, nothing moves. */
.post-pager[b-qxq77a12os] {
    display: grid;
    grid-template-columns: 1fr 1fr;
    gap: var(--space-3);
    max-width: 42rem;
    margin: var(--space-6) auto 0;
    padding-top: var(--space-4);
    border-top: 1px solid var(--color-border);
}

.post-pager-link[b-qxq77a12os] {
    display: flex;
    flex-direction: column;
    gap: var(--space-1);
    padding: var(--space-3) var(--space-4);
    border: 1px solid var(--color-border);
    border-radius: var(--radius);
    background: var(--color-bg);
    color: var(--color-text);
    text-decoration: none;
    transition: box-shadow var(--transition), border-color var(--transition);
}

.post-pager-link:hover[b-qxq77a12os] {
    border-color: var(--color-brand);
    box-shadow: var(--shadow-hover);
    color: var(--color-text);
}

.post-pager-next[b-qxq77a12os] {
    grid-column: 2;
    text-align: right;
}

.post-pager-label[b-qxq77a12os] {
    display: inline-flex;
    align-items: center;
    gap: var(--space-1);
    color: var(--color-text-soft);
    font-size: 0.85rem;
    font-weight: 700;
}

.post-pager-next .post-pager-label[b-qxq77a12os] {
    align-self: flex-end;
}

.post-pager-title[b-qxq77a12os] {
    color: var(--color-brand);
    font-weight: 700;
    line-height: 1.3;
}

/* On a phone the two cards stack: a half-width card would squeeze a long title
   into a narrow column. Older first, as in the wide layout. */
@media (max-width: 40rem) {
    .post-pager[b-qxq77a12os] {
        grid-template-columns: 1fr;
    }

    .post-pager-next[b-qxq77a12os] {
        grid-column: 1;
    }
}
/* /Features/Posts/PostList.razor.rz.scp.css */
/* The card is PostCard and the base list grid lives in the global app.css, shared
   with the home-page embed. Only the page's two-column layout is here: one column
   on a phone, two from tablet width, with the newest post across both. */
@media (min-width: 48rem) {
    .post-list-grid[b-j4litflynw] {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }

    .post-list-featured[b-j4litflynw] {
        grid-column: 1 / -1;
    }
}

/* Same centred 42rem reading column as a content page (ContentPage.razor.css), so
   every page of the site shares one column under the header. Two cards still fit
   side by side in it. */
h1[b-j4litflynw],
article[b-j4litflynw],
p[b-j4litflynw],
.post-list[b-j4litflynw] {
    max-width: 42rem;
    margin-inline: auto;
}

/* The intro's last paragraph drops its margin (app.css), so the first card would
   sit right under the text; this gives it the same air as between sections. */
article[b-j4litflynw] {
    margin-bottom: var(--space-5);
}
