Design system  /  Diagrams  /  cn-pair
11.08 · Diagrams / cn-pair

<cn-pair>

Two systems linked by an orange arrow. The integration-page headline diagram: name on the left, name on the right, and the bridge that connects them in the middle.

Canonical · the xWiki integration banner
<cn-pair
  left-label="Open Register"
  left-caption="nextcloud.example"
  right-label="xWiki"
  right-caption="xwiki.example"
  right-color="cobalt-700"
  bridge-label="OpenConnector integration">
  <svg slot="left-icon" ... />
  <svg slot="right-icon" ... />
</cn-pair>
Brand-pair · Nextcloud workspace ↔ Common Ground+
One-way · arrow="→"
API · slots
SlotPurpose
left-iconSVG glyph for the left hex. 24×24 viewBox, currentColor for stroke/fill so the icon inherits the hex ink.
right-iconSVG glyph for the right hex. Same rules as left.
API · attributes
AttributeValuesDefaultPurpose
left-labelstringStrong name under the left hex.
left-captionstringOptional Plex Mono code-style caption (e.g. domain or slug).
left-colorcobalt · cobalt-700 · cobalt-900 · nextcloud · commonground · mint · lavendercobaltHex fill on the left side. Use a sub-brand fill only for that brand's surface.
right-labelstringStrong name under the right hex.
right-captionstringRight caption.
right-colorsee left-colorcobalt-700Hex fill on the right side.
bridge-labelstringText directly under the arrow. Names the integration / bridge.
arrowany glyph ( · · )The bridge arrow. Always KNVB orange; the component owns the one-orange-per-scene budget.
Why we built it this way
Pair · the integration headline

The orange arrow is the brand element

Every Conduction integration page opened with the same pattern, hand-rolled in each docs site: two hexes, a bridge, a centred orange arrow. cn-pair encodes that pattern so the brand rules can't drift.