/*
 * templates/industry.css -- page-type-specific rules for the 'industry' entity type.
 * Part 4 of the load order in docs/DESIGN_SYSTEM.md ("File architecture /
 * load order"): loads after tokens.css, base.css and components.css. Only
 * ADDS rules; every value references a tokens.css variable (var(--...)).
 * The shared page-module primitives this template relies on (.page-head,
 * .module-grid/.module, .stat/.stat-grid, .bullet-list, .related-grid,
 * .card-list, .risk-item, .source-list, .not-available) already live in
 * components.css -- reused as-is, not duplicated here. This file only holds
 * flourishes unique to the long industry module list: PESTLE as a labelled
 * 2x3 grid (via .subfield-grid, already generic) and a subsector-count badge
 * on the "Subsectors" section.
 */

/* pestle is authored as an assoc object of 6 keys (political/economic/
   social/technological/legal/environmental), which render_subfields() turns
   into .subfield-grid/.subfield -- lay those 6 out 3-per-row on industry
   pages instead of the 1-column stack default. */
.module[data-key="pestle"] .subfield-grid{
  display:grid;grid-template-columns:repeat(3,1fr);gap:20px 24px;
}

/* forecast_scenarios (conservative/base/aggressive) gets the same treatment,
   read left-to-right from most to least conservative. */
.module[data-key="forecast_scenarios"] .subfield-grid{
  display:grid;grid-template-columns:repeat(3,1fr);gap:20px 24px;
}

@media(max-width:720px){
  .module[data-key="pestle"] .subfield-grid,
  .module[data-key="forecast_scenarios"] .subfield-grid{grid-template-columns:1fr}
}