/* Springhouse.com - global site stylesheet
   This is a minimal placeholder. Full design system / branding pass is tracked under
   section 2 (site-wide shell & navigation) and section 3/4 (home + marketing pages) in
   Requirements/frontend-blazor-task-list.md. */

html, body {
    margin: 0;
    padding: 0;
    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
    color: #1b1b1b;
    /* Guards against the sub-pixel horizontal scrollbar some browsers introduce with the
       100vw "full-bleed" breakout trick (used by Home.razor.css to let hero/band sections
       span the full viewport width from inside the width-capped <main class="site-main">
       container) - see MainLayout.razor.css. Safe sitewide since nothing here is meant to
       scroll horizontally. */
    overflow-x: hidden;
}

a {
    color: #1b2a4a;
}

h1, h2, h3, h4 {
    font-weight: 600;
}

.content {
    padding-top: 1.1rem;
}

.valid.modified:not([type=checkbox]) {
    outline: 1px solid #26b050;
}

.invalid {
    outline: 1px solid red;
}

.validation-message {
    color: red;
}

#blazor-error-ui {
    color-scheme: light only;
}

/* Accessibility utilities (task-list section 10's "Accessibility pass (WCAG)" bullet,
   2026-08-09 session). Global/non-isolated on purpose: Blazor CSS isolation scopes a
   *.razor.css file to only that component's own rendered markup, but these two classes
   need to be usable from any component (MainLayout's skip link, SiteFooter's external-link
   hints, Home.razor's link-context text, Register.razor's visually-hidden field labels,
   etc.) - a single global definition avoids copy-pasting the same rule into half a dozen
   .razor.css files. (SiteHeader.razor.css already had its own private .visually-hidden for
   the search box's hidden label before this session - that one is untouched/left as-is
   since it's harmless duplication scoped to just that component, not worth churning.) */
.visually-hidden {
    position: absolute;
    width: 1px;
    height: 1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    white-space: nowrap;
}

/* Skip-to-content link (MainLayout.razor) - standard "hidden until keyboard-focused"
   pattern so keyboard/screen-reader users can bypass the header/nav on every single page
   instead of tabbing through the full utility bar + primary nav (with its multi-level
   dropdowns - see NavMenuItem.razor.css) every time. Positioned fixed top-left, off-screen
   until :focus, matching the same "visually hidden but present" idea as .visually-hidden
   above but needs its own rule since it must become visible on focus rather than staying
   hidden. */
.skip-link {
    position: absolute;
    top: -3rem;
    left: 0.5rem;
    z-index: 1000;
    background: #1b2a4a;
    color: #ffffff;
    padding: 0.6rem 1rem;
    border-radius: 0 0 4px 4px;
    text-decoration: none;
    font-weight: 600;
}

.skip-link:focus {
    top: 0;
}

/* Course catalog (task-list section 5) - shared, NOT CSS-isolated, because
   CourseCatalog.razor (listing) and CourseCatalogCategory.razor (category-browse) are two
   separate components that need to look identical - Blazor CSS isolation scopes a
   .razor.css file to only its own component's markup, so putting these here once is
   simpler and more correct than maintaining two copies in sync across two .razor.css
   files. */
.catalog-title {
    color: #1b2a4a;
    margin: 0.5rem 0 0.5rem;
}

.search-summary {
    color: #333333;
    margin: 0 0 1.5rem;
}

.catalog-intro {
    color: #333333;
    font-size: 1rem;
    max-width: 700px;
    margin: 0 0 1.5rem;
}

.catalog-layout {
    display: grid;
    grid-template-columns: 260px 1fr;
    gap: 2rem;
    align-items: start;
    margin-top: 1rem;
}

.course-grid {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 1.5rem;
}

.catalog-empty {
    color: #333333;
    padding: 2rem 0;
}

@media (max-width: 900px) {
    .catalog-layout {
        grid-template-columns: 1fr;
    }

    .course-grid {
        grid-template-columns: repeat(2, 1fr);
    }
}

@media (max-width: 560px) {
    .course-grid {
        grid-template-columns: 1fr;
    }
}

/* Schedule/calendar listing (task-list section 7) - shared, NOT CSS-isolated, same
   reasoning as ".catalog-layout" above: Schedule.razor and UpcomingEvents.razor are two
   separate components that need to render date-grouped session lists identically. Reuses
   ".catalog-title"/".catalog-intro"/".catalog-layout"/".catalog-main"/".catalog-empty"
   from the course-catalog rules above rather than a parallel set of "schedule-*"
   equivalents for the same generic sidebar+main two-column shape - only what's genuinely
   new to this page (date grouping, the session-row list container) gets its own rules
   here. ".catalog-sidebar" itself has never had its own rules (the course catalog page
   doesn't style it either - ".catalog-layout"'s grid-template-columns positions it, and
   ScheduleCategoryFilter.razor/CourseCatalogSidebar.razor each style their own inner
   content), so no new rule is added for it here. */

.schedule-date-group {
    margin: 0 0 2rem;
}

.schedule-date-heading {
    font-size: 1.05rem;
    color: #1b2a4a;
    border-bottom: 1px solid #e2e6ee;
    padding-bottom: 0.4rem;
    margin: 0 0 0.75rem;
}

.schedule-session-list {
    list-style: none;
    margin: 0;
    padding: 0;
}

/* Consulting landing + sub-pages (task-list section 4). Shared, NOT CSS-isolated -
   RelatedConsultingServices.razor is one component but reused across 8 separate routed
   pages (landing + 7 sub-pages), and the body/lead-form/tier-comparison rules below are
   duplicated inline markup patterns across those same 8 pages (see each page's own doc
   comment - not a single shared component since their body content genuinely differs in
   shape). Global classes here avoid keeping 8 sets of isolated rules in sync by hand, same
   reasoning already established above for ".catalog-*"/".schedule-*". */
.consulting-body {
    max-width: 760px;
}

.consulting-body h2 {
    color: #1b2a4a;
    font-size: 1.15rem;
    margin: 1.75rem 0 0.6rem;
}

.consulting-body h2:first-child {
    margin-top: 0;
}

.consulting-body p {
    color: #333333;
    line-height: 1.6;
    margin: 0 0 1rem;
}

.consulting-body ul {
    color: #333333;
    line-height: 1.6;
    margin: 0 0 1rem;
}

.consulting-body ul ul {
    margin-top: 0.4rem;
}

.consulting-lead-form {
    max-width: 700px;
    margin: 0.5rem 0 2rem;
}

.consulting-lead-form h2 {
    color: #1b2a4a;
    font-size: 1.1rem;
    margin: 0 0 0.4rem;
}

.consulting-lead-form p {
    color: #333333;
    margin: 0 0 1rem;
}

.consulting-lead-form iframe {
    width: 100%;
    height: 620px;
    border: none;
}

.consulting-tier-grid {
    display: grid;
    grid-template-columns: repeat(2, 1fr);
    gap: 1.25rem;
    max-width: 760px;
    margin: 0 0 1.5rem;
}

.consulting-tier-card {
    background: #f4f6fb;
    border-radius: 4px;
    padding: 1.25rem 1.5rem;
}

.consulting-tier-card h3 {
    margin: 0 0 0.2rem;
    color: #1b2a4a;
    font-size: 1rem;
}

.consulting-tier-price {
    font-weight: 700;
    color: #2d4a8a;
    margin: 0 0 0.6rem;
}

.consulting-tier-card ul {
    margin: 0;
    padding-left: 1.1rem;
    color: #333333;
    line-height: 1.5;
}

.consulting-steps {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 1rem;
    max-width: 900px;
    margin: 0 0 2rem;
}

.consulting-step-card {
    background: #f4f6fb;
    border-radius: 4px;
    padding: 1.1rem 1.25rem;
}

.consulting-step-card h3 {
    margin: 0 0 0.4rem;
    color: #1b2a4a;
    font-size: 0.95rem;
}

.consulting-step-card p {
    margin: 0;
    color: #333333;
    line-height: 1.5;
    font-size: 0.9rem;
}

.consulting-related {
    margin-top: 2.5rem;
    padding-top: 2rem;
    border-top: 1px solid #e2e6ee;
}

.consulting-related h2 {
    color: #1b2a4a;
    font-size: 1.1rem;
    margin: 0 0 1rem;
}

.consulting-related-grid {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 0.75rem;
}

.consulting-related-card {
    display: block;
    padding: 0.9rem 1rem;
    background: #f4f6fb;
    border-radius: 4px;
    color: #2d4a8a;
    font-weight: 600;
    text-decoration: none;
    font-size: 0.9rem;
}

.consulting-related-card:hover {
    background: #e8ecf7;
    text-decoration: underline;
}

@media (max-width: 900px) {
    .consulting-tier-grid,
    .consulting-steps {
        grid-template-columns: 1fr;
    }

    .consulting-related-grid {
        grid-template-columns: repeat(2, 1fr);
    }
}

@media (max-width: 560px) {
    .consulting-related-grid {
        grid-template-columns: 1fr;
    }
}

/* Shared (not CSS-isolated) since it's used both by Routes.razor's in-app <NotFound>
   fragment and by the /not-found page rendered via UseStatusCodePagesWithReExecute for
   direct/first-hit requests to unmatched URLs - see Program.cs. */
.not-found {
    text-align: center;
    padding: 3rem 1rem;
}

.not-found h1 {
    font-size: 4rem;
    margin: 0;
    color: #1b2a4a;
}

.not-found p {
    font-size: 1rem;
    color: #444444;
}

/* Expert Training landing + sub-pages (task-list section 4, "Training landing page +
   sub-pages" bullet). Shared, NOT CSS-isolated - same reasoning already established above
   for ".consulting-*": RelatedTrainingServices.razor is one component reused across 10
   separate routed pages, and the body/lead-form markup pattern below is duplicated inline
   across those same 10 pages (see each page's own doc comment).

   Deliberately a NEW ".training-*" prefix rather than reusing ".consulting-body"/
   ".consulting-lead-form" directly, even though the rules are visually identical - unlike
   ".catalog-title"/".catalog-intro" (genuinely generic sitewide typographic classes used
   from the very first session), "consulting-body"/"consulting-lead-form" were named after
   one specific content vertical, and reusing an IT-Consulting-prefixed class on Training
   pages would read as a mistake to a future maintainer grepping for "consulting-".
   RelatedTrainingServices.razor is the one exception - see that component's own doc
   comment for why it reuses ".consulting-related*" directly instead. */
.training-body {
    max-width: 760px;
}

.training-body h2 {
    color: #1b2a4a;
    font-size: 1.15rem;
    margin: 1.75rem 0 0.6rem;
}

.training-body h2:first-child {
    margin-top: 0;
}

.training-body p {
    color: #333333;
    line-height: 1.6;
    margin: 0 0 1rem;
}

.training-body ul {
    color: #333333;
    line-height: 1.6;
    margin: 0 0 1rem;
}

.training-body ul ul {
    margin-top: 0.4rem;
}

/* "Learn Design Thinking" / "Browse Power Sessions" style CTA buttons that several
   Training sub-pages use to link into the course catalog (task-list section 5) - the live
   site renders these as buttons, not plain inline text links, so this small pill-style
   treatment (matching ".consulting-related-card"'s existing color/weight) carries that
   forward rather than flattening it to a plain <a>. */
.training-cta-links {
    display: flex;
    flex-wrap: wrap;
    gap: 0.75rem;
    margin: 0 0 1.5rem;
}

.training-cta-link {
    display: inline-block;
    padding: 0.65rem 1.25rem;
    background: #2d4a8a;
    color: #ffffff;
    border-radius: 4px;
    font-weight: 600;
    text-decoration: none;
    font-size: 0.9rem;
}

.training-cta-link:hover {
    background: #1b2a4a;
}

.training-lead-form {
    max-width: 700px;
    margin: 0.5rem 0 2rem;
}

.training-lead-form h2 {
    color: #1b2a4a;
    font-size: 1.1rem;
    margin: 0 0 0.4rem;
}

.training-lead-form p {
    color: #333333;
    margin: 0 0 1rem;
}

.training-lead-form iframe {
    width: 100%;
    height: 620px;
    border: none;
}

/* Menu of private-event workshop topics (Corporate Training Plans / Private Learning and
   Development Events sub-page only) - a 5-category list of short workshop titles. Reuses
   ".training-body ul" for the item styling; this just adds the category-heading spacing
   since ".training-body h3" has no rule of its own yet (nothing else in this cluster needed
   an h3 until this page). */
.training-topic-menu h3 {
    color: #1b2a4a;
    font-size: 1rem;
    margin: 1.25rem 0 0.4rem;
}

@media (max-width: 560px) {
    .training-cta-links {
        flex-direction: column;
        align-items: flex-start;
    }
}