/**
 * PER-PAGE CSS for the SERVICE LANDING page family — and for nothing
 * else. Loaded ONLY on the templates listed in $tbi_ai_service_landing_templates
 * in functions.php (everything in service-landing-pages/).
 *
 * Do not put hire-page or service-INNER CSS in this file. The three
 * families each have exactly one file and are never mixed:
 *
 *   css/hire-common.css            -> hire pages          (body.hire-figma-page)
 *   css/service-inner-common.css   -> service inner pages (body.service-inner-page)
 *   css/service-landing-common.css -> service landing     (body.service-landing-page)
 *
 * Cross-family component CSS is NOT repeated here — it lives in
 * css/figma-pages-base.css: every hrf-* section under body.tbi-figma-page,
 * and the svcl-* service components (hero review card, catalog grid,
 * platform grid, insights) under body.tbi-service-page. This file holds
 * only what genuinely differs per landing page, which in practice is
 * background-image url()s for the hrf-hero / hrf-testi / hrf-cta2 /
 * hrf-faq sections plus the occasional svcl-* catalog background.
 *
 * Each block stays scoped under its own body.page-template-* class, which
 * body_class() derives from the sanitized template filename regardless of
 * subfolder — so service-landing-pages/page-services-landing-foo.php is
 * body.page-template-page-services-landing-foo, with no folder segment.
 *
 * Adding a new landing page: add its template filename to
 * $tbi_ai_service_landing_templates (used by both the enqueue block and the
 * body-class filter), then add ONE new scoped block at the end of this
 * file. Do NOT create a new page-specific stylesheet, and do NOT add the
 * rule to figma-pages-base.css unless it is identical across families.
 *
 * A rule identical for EVERY landing page but for no other family belongs
 * in this file scoped to body.service-landing-page, not repeated per page.
 *
 * History: split out of the mixed css/hire-common.css and the former
 * css/services-common.css on 2026-09-16. Where a page had a block in both
 * of those files, both blocks are kept verbatim and placed adjacently
 * under that page below. Every block is byte-identical to its pre-split
 * form.
 */

/* --- page-services-ecommerce-development-company.php ---
   Fourth page in the Services Landing Page family, built from
   service-landing-pages-content/ecommerce_development_company.md — no
   Figma source. All four backgrounds are the shared design-system assets
   copied verbatim from assets/images/services-ecommerce/, same "design —
   copy from base" rule as the other clones above. This page also reuses
   hrf-risk and svcl-platforms (both flat-color/no background image). */

body.page-template-page-services-ecommerce-development-company .hrf-hero {
  background-image: url("../assets/images/services-ecommerce-development-company/hero-bg.png");
}

body.page-template-page-services-ecommerce-development-company .hrf-testi {
  background-image: url("../assets/images/services-ecommerce-development-company/testi-bg.png");
}

body.page-template-page-services-ecommerce-development-company .hrf-cta2 {
  background-image: url("../assets/images/services-ecommerce-development-company/cta-mid-bg.png");
}

body.page-template-page-services-ecommerce-development-company .hrf-faq {
  background-image: url("../assets/images/services-ecommerce-development-company/faq-bg.png");
}

/* --- page-services-ecommerce-development-company.php ---
   This page's own brief supplies real C16 content, so svcl-catalog ships
   with its own 11-item grid, real URLs and all — but no Figma frame exists
   to export a fresh background texture from, so this reuses
   page-services-ecommerce.php's own catalog-bg.svg verbatim (copied into
   this page's own asset folder, same allowance used for the bigcommerce
   page above). svcl-platforms also ships fresh C18 card content but no
   background image of its own (flat white section, no override needed). */

body.page-template-page-services-ecommerce-development-company .svcl-catalog__bg {
  content: url("../assets/images/services-ecommerce-development-company/catalog-bg.svg");
}

/* --- service-landing-pages/page-services-landing-software-development.php ---
   Second page in the service-landing-pages/ folder, built from
   service-landing-pages-content/software_development_services.md — no Figma
   source. All four backgrounds are the shared design-system assets copied
   verbatim from assets/images/services-ecommerce-development-company/, the
   same "design — copy from base" rule as the other clones above. This page
   also uses hrf-risk and svcl-platforms (both flat-colour, no background
   image of their own). */

body.page-template-page-services-landing-software-development .hrf-hero {
  background-image: url("../assets/images/services-software-development/hero-bg.png");
}

body.page-template-page-services-landing-software-development .hrf-testi {
  background-image: url("../assets/images/services-software-development/testi-bg.png");
}

body.page-template-page-services-landing-software-development .hrf-cta2 {
  background-image: url("../assets/images/services-software-development/cta-mid-bg.png");
}

body.page-template-page-services-landing-software-development .hrf-faq {
  background-image: url("../assets/images/services-software-development/faq-bg.png");
}

/* --- service-landing-pages/page-services-landing-software-development.php ---
   This page's own brief supplies real C16 content, so svcl-catalog ships
   with its own 6-item routing grid and real child-service URLs — but no
   Figma frame exists to export a fresh background texture from, so this
   reuses page-services-ecommerce.php's own catalog-bg.svg verbatim (copied
   into this page's own asset folder, same allowance used by the clones
   above). svcl-platforms carries fresh, brief-sourced card content but has
   no background image of its own (flat white section, no override needed);
   svcl-insights carries the base page's own fallback content unchanged. */

body.page-template-page-services-landing-software-development .svcl-catalog__bg {
  content: url("../assets/images/services-software-development/catalog-bg.svg");
}

/* --- service-landing-pages/page-services-landing-mobile-app-development-company.php ---
   Third page in the service-landing-pages/ folder, built from
   service-landing-pages-content/mobile_app_development_company.md — no Figma
   source. All four backgrounds are the shared design-system assets copied
   verbatim from assets/images/services-ecommerce-development-company/, the
   same "design — copy from base" rule as the other clones above. The asset
   folder is named for the brief's own vertical slug
   (services-mobile-app-development-company), not for the "landing-" prefix
   this template's filename carries — the selector below still uses the
   sanitized template filename, which is what WordPress derives the
   page-template-* body class from. This page also uses hrf-risk and
   svcl-platforms (both flat-colour, no background image of their own). */

body.page-template-page-services-landing-mobile-app-development-company .hrf-hero {
  background-image: url("../assets/images/services-mobile-app-development-company/hero-bg.png");
}

body.page-template-page-services-landing-mobile-app-development-company .hrf-testi {
  background-image: url("../assets/images/services-mobile-app-development-company/testi-bg.png");
}

body.page-template-page-services-landing-mobile-app-development-company .hrf-cta2 {
  background-image: url("../assets/images/services-mobile-app-development-company/cta-mid-bg.png");
}

body.page-template-page-services-landing-mobile-app-development-company .hrf-faq {
  background-image: url("../assets/images/services-mobile-app-development-company/faq-bg.png");
}

/* --- service-landing-pages/page-services-landing-mobile-app-development-company.php ---
   This page's own brief supplies real C16 content, so svcl-catalog ships
   with its own 10-item routing grid (4 real child-service URLs, 6 the brief
   itself marks "TO CONFIRM") — but no Figma frame exists to export a fresh
   background texture from, so this reuses page-services-ecommerce.php's own
   catalog-bg.svg verbatim, copied into this page's own asset folder the same
   way as the clones above. svcl-platforms carries fresh C18 card content and
   svcl-insights three real, brief-sourced article cards; neither has a
   background image of its own, so neither needs an override. */

body.page-template-page-services-landing-mobile-app-development-company .svcl-catalog__bg {
  content: url("../assets/images/services-mobile-app-development-company/catalog-bg.svg");
}

/* --- service-landing-pages/page-services-landing-web-development.php ---
   Built from service-landing-pages-content/web_development.md (RECIPE: HUB) —
   no Figma source. All four backgrounds are the shared design-system assets
   copied verbatim from assets/images/services-ecommerce/, same "design — copy
   from base" rule as the other clones above. This page also uses hrf-risk (C5,
   flat color, no background image) and omits hrf-hth (no C13 in the brief).
   Note the selector carries no `service-landing-pages/` path segment:
   body_class() derives page-template-* from the sanitized basename regardless
   of which subfolder the template file lives in (SERVICE_PAGE_TEMPLATE.md
   §5.4). */

body.page-template-page-services-landing-web-development .hrf-hero {
  background-image: url("../assets/images/services-web-development/hero-bg.png");
}

body.page-template-page-services-landing-web-development .hrf-testi {
  background-image: url("../assets/images/services-web-development/testi-bg.png");
}

body.page-template-page-services-landing-web-development .hrf-cta2 {
  background-image: url("../assets/images/services-web-development/cta-mid-bg.png");
}

body.page-template-page-services-landing-web-development .hrf-faq {
  background-image: url("../assets/images/services-web-development/faq-bg.png");
}

/* --- service-landing-pages/page-services-landing-web-development.php ---
   This page's own brief supplies real C16 content, so svcl-catalog ships with
   its own 5-item routing grid and real child-service URLs — but no Figma frame
   exists to export a fresh background texture from, so this reuses
   page-services-ecommerce.php's own catalog-bg.svg verbatim (copied into this
   page's own asset folder, per SERVICE_PAGE_TEMPLATE.md §3's "the same
   background texture asset can be reused too" allowance). svcl-platforms and
   svcl-insights carry the base page's own fallback content unchanged (the
   brief's own UNPLACED list omits C18 and C17 outright) — neither has a
   background image of its own, flat white sections, no override needed. */

body.page-template-page-services-landing-web-development .svcl-catalog__bg {
  content: url("../assets/images/services-web-development/catalog-bg.svg");
}

/* --- service-landing-pages/page-services-landing-artificial-intelligence-development.php ---
   Built from
   service-landing-pages-content/artificial_intelligence_development_services.md
   (RECIPE: HUB) — no Figma source. All four backgrounds are the shared
   design-system assets copied verbatim from assets/images/services-ecommerce/,
   same "design — copy from base" rule as the other clones above. This page
   also uses hrf-risk (C5, flat colour, no background image) and omits hrf-hth
   (no C13 in the brief). The asset folder is named for the brief's own
   vertical slug (services-artificial-intelligence-development), not for the
   "landing-" prefix the template filename carries; the selector below still
   uses the sanitized template filename, which is what body_class() derives
   page-template-* from regardless of subfolder (SERVICE_PAGE_TEMPLATE.md
   §5.4). */

body.page-template-page-services-landing-artificial-intelligence-development .hrf-hero {
  background-image: url("../assets/images/services-artificial-intelligence-development/hero-bg.png");
}

body.page-template-page-services-landing-artificial-intelligence-development .hrf-testi {
  background-image: url("../assets/images/services-artificial-intelligence-development/testi-bg.png");
}

body.page-template-page-services-landing-artificial-intelligence-development .hrf-cta2 {
  background-image: url("../assets/images/services-artificial-intelligence-development/cta-mid-bg.png");
}

body.page-template-page-services-landing-artificial-intelligence-development .hrf-faq {
  background-image: url("../assets/images/services-artificial-intelligence-development/faq-bg.png");
}

/* --- service-landing-pages/page-services-landing-artificial-intelligence-development.php ---
   This page's own brief supplies real C16 content, so svcl-catalog ships with
   its own 9-item routing grid and real child-service URLs — but no Figma frame
   exists to export a fresh background texture from, so this reuses
   page-services-ecommerce.php's own catalog-bg.svg verbatim (copied into this
   page's own asset folder, per SERVICE_PAGE_TEMPLATE.md §3's "the same
   background texture asset can be reused too" allowance). svcl-platforms and
   svcl-insights carry the base page's own fallback content unchanged (this
   brief marks both C18 and C17 OMITTED) — neither has a background image of
   its own, flat white sections, no override needed. */

body.page-template-page-services-landing-artificial-intelligence-development .svcl-catalog__bg {
  content: url("../assets/images/services-artificial-intelligence-development/catalog-bg.svg");
}