App cross-links
One component connects the three surfaces a visitor lands on while learning about a Conduction app: the product page, the documentation site, and the academy. URLs come from the shared apps-registry so the cards stay in lockstep across surfaces. Two variants: a rail card for the right column of a product detail page, and an inline block for the bottom of an academy post or a docs page.
<AppCrossLinks variant="rail"/>Shown next to the body content on /apps/<slug>.mdx. The "Open product page" row is omitted (surface="product") so the user is never linked to the page they're already on.
One catalogue, every register, every public link. Connect OpenCatalogi to your registers, configure once, and your team is publishing searchable entries the same morning. Citizens land at jouwgemeente.nl/catalogi and find what they need without writing a Woo-verzoek.
[ … rest of the page body … ]
<AppCrossLinks variant="inline"/>Page-bottom block on academy posts and docs overview pages. With a single app, the row of cards collapses to one card. The "Read in the academy" row is omitted (surface="academy") because we're already on an academy post.
<AppCrossLinks apps={[…]}/>A post that covers a pipeline across two apps gets two cards in a responsive grid. Shown here on a docs page footer (surface="docs"), so each card omits the "Read the documentation" row.