/* ═══════════════════════════════════════════════════════════════════════════
   STANDALONE TOPIC PAGES — 2026 design system
   Geomage Website (www.geomage.com)

   Loaded by the standalone topic pages ALONGSIDE main.css and pages/product.css
   (frontend/fwi-rtm.html is the first; the remaining g-Platform / g-Space /
   g-Viewer topics are meant to follow the same shape). Those pages are built
   entirely from design-system components — hero, section-head, mod-cards,
   packages, workflow, specs, faq, cta — so this sheet exists only for the one
   thing the component set does not already cover.

   WHY ITS OWN FILE, not more of pages/product.css:
   product.css is documented as "loaded by every product template", and it says
   in its own header that page-unique rules go in pages/<page>.css, never there.
   Putting a topic-page rule in it would ship these bytes to all three product
   templates that never render the markup. A separate sheet also gives the 23
   remaining conversions one file to link and one place to grow.

   Kept deliberately small. If a topic page wants something new, prefer adding a
   modifier to the design-system component that owns the pattern.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── SIBLING-CAPABILITY STRIP ────────────────────────────────────────────────
   The "More g-Platform capabilities" row: the same chip links a module card
   carries (.mod__topic, styled in pages/product.css), but standing on their own
   inside a section instead of sitting at the foot of a .mod card.

   .mod__topics is built for that card footing — it draws a rule above itself
   and reserves the space for it. Lifted out of the card there is nothing above
   to separate from, and the row reads as a centred cluster rather than a
   left-aligned card detail. This modifier removes the footing and centres the
   run; everything else (chip shape, colour, hover, the --primary variant) is
   inherited untouched.

   The links here are plain <a href> only. Standalone URLs are excluded from the
   SSR topic-switcher whitelist, and a standalone page is emitted without the
   switcher script at all, so these must never carry data-topic — the e2e suite
   asserts a standalone page ships none. */
.mod__topics--strip {
  justify-content: center;
  gap: 10px;
  margin-top: 0;
  padding-top: 0;
  border-top: none;
}

/* ── RESPONSIVE ──────────────────────────────────────────────────────────── */
@media (max-width: 720px) {
  /* Left-align once the chips wrap onto many short rows: a centred ragged
     stack of 14 pills is harder to scan than a flush-left one. */
  .mod__topics--strip { justify-content: flex-start; gap: 8px; }
}