.elementor-widget-theme-post-featured-image .widget-image-caption{color:var( --e-global-color-text );font-family:var( --e-global-typography-text-font-family ), Sans-serif;font-weight:var( --e-global-typography-text-font-weight );}.elementor-706 .elementor-element.elementor-element-1072035{--display:flex;}/* Start custom CSS *//* ---- archive sidebar: show only the taxonomy that matches the archive ----
   706 is a single archive template assigned include/general, so it renders on
   every term archive. Its sidebar stacks three term loops, one per CPT
   taxonomy, and they already carried .custom-cat plus .blog-only /
   .news-only / .case-studies-only - but nothing ever hid them, so
   /blog/sector/<term>/ also listed the News and Case Studies terms
   (12 rows instead of 9).

   WordPress puts tax-<taxonomy> on <body> for a term archive
   (tax-sector, tax-news-sector, tax-case-studies-sector - verified), so each
   loop can be hidden on the archives it does not belong to.

   Written as explicit hides rather than a blanket .custom-cat{display:none}
   with opt-in shows: if a future archive context carries none of these body
   classes the sidebar still renders all three (today's behaviour) instead of
   collapsing to empty. */
body.tax-sector .custom-cat.news-only,
body.tax-sector .custom-cat.case-studies-only,
body.tax-news-sector .custom-cat.blog-only,
body.tax-news-sector .custom-cat.case-studies-only,
body.tax-case-studies-sector .custom-cat.blog-only,
body.tax-case-studies-sector .custom-cat.news-only{display:none!important;}/* End custom CSS */