/* ============================================================
   components/topic-strip.css
   The topic strip before the footer: one band, one line, one
   destination. Rendered at the end of an article, an insight
   or a case, where the reader has finished the piece and the
   subject is worth naming as a body of work.

   It is a LINK, whole. Nothing inside it is separately
   clickable, so nothing inside it may look as though it is.
   ============================================================ */
.rfi-topic-strip {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  margin: 34px 0 0;
  padding: 18px var(--rfi-pad-card);
  background: var(--rfi-navy-tint);
  border-radius: var(--rfi-radius);
  text-decoration: none;
  color: var(--rfi-text);
  transition: box-shadow .16s ease, transform .16s ease;
}

/* The one hover motion on the site, and the shadow that goes with it. The band does not
   change colour on hover: it is already a tinted surface, and a second tint would read as
   a state rather than as a lift. */
.rfi-topic-strip:hover {
  transform: var(--rfi-lift);
  box-shadow: var(--rfi-shadow);
}

.rfi-topic-strip__text {
  font-family: var(--rfi-font-ui);
  font-size: 15.5px;
  font-weight: 500;
  line-height: 1.4;
  min-width: 0;   /* so a long list wraps instead of pushing the arrow out of the band */
}

/* The arrow is the affordance, not a second control: aria-hidden in the markup, because the
   link already reads as a link and the glyph would only repeat it to a screen reader. */
.rfi-topic-strip__arrow {
  flex: 0 0 auto;
  font-size: 18px;
  line-height: 1;
  color: var(--rfi-navy);
  transition: transform .16s ease;
}

.rfi-topic-strip:hover .rfi-topic-strip__arrow { transform: translateX(3px); }

@media (max-width: 640px) {
  .rfi-topic-strip { padding: 15px 14px; gap: 12px; }
  .rfi-topic-strip__text { font-size: 14.5px; }
}
