VERIFICATION-0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
Relationships · Extended localized content for verification and layout resilience
Selected entity: Billing
- Depends on
- Chrona
- Publishes to
- Summa
- Owned by
- Finance domain
<forma-relationship-index>
Provides a semantic non-spatial index of entity relationships and their direction.
<forma-relationship-index>patterns/relationship-index.htmlA relationship index lists the relationships of one selected entity as text: each row names a relationship type with its direction (Depends on, Depended on by, Publishes to) and links to the related entities. It is the non-spatial equivalent of the lines in a Diagram or Spatial canvas, so users who cannot see or navigate the drawing still get the complete set of connections. Forma lays it out as a description list; the relationships, their direction wording and their order come from the application's model.
div with the relationship type as a bold dt (minmax(7rem, 10rem)) and targets in a dd with no indent.The smallest correct markup: the canonical pattern from patterns/relationship-index.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
Selected entity: Billing
<forma-relationship-index class="forma-component-tag">
<section class="forma-relationship-index" aria-labelledby="relationships-title">
<header><h2 id="relationships-title">Relationships</h2><p>Selected entity: Billing</p></header>
<dl class="forma-relationship-index__list">
<div><dt>Depends on</dt><dd><a href="#chrona">Chrona</a></dd></div>
<div><dt>Publishes to</dt><dd><a href="#summa">Summa</a></dd></div>
<div><dt>Owned by</dt><dd><a href="#finance">Finance domain</a></dd></div>
</dl>
</section>
</forma-relationship-index>
Click or tap the code once to select all of it, then copy.
Both directions for the Billing service. Outgoing (Depends on) and incoming (Depended on by) are distinct relationship names, and several targets share a row as a comma-separated list of links. A relationship with no targets says None recorded.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
Direction is stated from Billing's point of view.
<forma-relationship-index class="forma-component-tag">
<section class="forma-relationship-index" aria-labelledby="relationship-index-incoming-and-outgoing-title">
<header><h2 id="relationship-index-incoming-and-outgoing-title">Relationships of Billing</h2><p>Direction is stated from Billing's point of view.</p></header>
<dl class="forma-relationship-index__list">
<div><dt>Depends on</dt><dd><a href="#relationship-index-incoming-and-outgoing-chrona">Chrona</a>, <a href="#relationship-index-incoming-and-outgoing-ledger">Ledger</a></dd></div>
<div><dt>Depended on by</dt><dd><a href="#relationship-index-incoming-and-outgoing-summa">Summa</a>, <a href="#relationship-index-incoming-and-outgoing-portal">Customer portal</a>, <a href="#relationship-index-incoming-and-outgoing-reports">Finance reports</a></dd></div>
<div><dt>Publishes to</dt><dd><a href="#relationship-index-incoming-and-outgoing-events">invoice.events topic</a></dd></div>
<div><dt>Replaces</dt><dd>None recorded</dd></div>
</dl>
</section>
</forma-relationship-index>
Click or tap the code once to select all of it, then copy.
The index sits under a system map and updates with the selected node. The header names the selection and states that the list mirrors the diagram's connections, including one the diagram marks as unverified.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
Selected: Payments gateway. Lists every connector drawn in the system map.
<forma-relationship-index class="forma-component-tag">
<section class="forma-relationship-index" aria-labelledby="relationship-index-diagram-equivalent-title">
<header><h2 id="relationship-index-diagram-equivalent-title">Connections of the selected node</h2><p>Selected: Payments gateway. Lists every connector drawn in the system map.</p></header>
<dl class="forma-relationship-index__list">
<div><dt>Sends requests to</dt><dd><a href="#relationship-index-diagram-equivalent-bank">Bank connector</a></dd></div>
<div><dt>Receives from</dt><dd><a href="#relationship-index-diagram-equivalent-checkout">Checkout</a></dd></div>
<div><dt>Reports to</dt><dd><a href="#relationship-index-diagram-equivalent-monitoring">Monitoring</a> (unverified: last seen 3 days ago)</dd></div>
</dl>
</section>
</forma-relationship-index>
Click or tap the code once to select all of it, then copy.
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
The index at phone width, where each relationship type sits above its targets.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
dd wrap as inline links; keep link text meaningful so each is a usable tap target.<forma-relationship-index class="forma-component-tag">
<section class="forma-relationship-index" aria-labelledby="relationship-index-mobile-relationships-title">
<header><h2 id="relationship-index-mobile-relationships-title">Relationships</h2><p>Selected entity: Customer record</p></header>
<dl class="forma-relationship-index__list">
<div><dt>Owned by</dt><dd><a href="#relationship-index-mobile-relationships-sales">Sales domain</a></dd></div>
<div><dt>Referenced by</dt><dd><a href="#relationship-index-mobile-relationships-invoices">Invoices</a>, <a href="#relationship-index-mobile-relationships-tickets">Support tickets</a></dd></div>
</dl>
</section>
</forma-relationship-index>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-labelledby | section.forma-relationship-index | id of the header heading | — | Names the index, ideally including the selected entity. |
href | a | URL or fragment | — | Each related entity links to its own view or to its node. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-relationship-index | Block class | — | Root section; a grid with 0.75rem gaps. Removes the trailing margin of the header's last child. |
.forma-relationship-index__list | Element class | — | The dl. Each div row is a two-column grid (minmax(7rem, 10rem) type, flexible targets); dt is semibold and dd has no margin. Rows stack at 30rem and below. |
| Keys | Result |
|---|---|
| Tab | Moves through the links to related entities. |
| Enter | Follows the focused link (native). |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Relationship with targets | dt plus dd containing links | Type and linked entities. |
| No targets | application text such as None recorded | Stated in words so absence is explicit. |
| Stacked | viewport ≤ 30rem | Type above targets. |
dd per row; list several targets inside it.dd elements in one row; the grid places the second one under the type.Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.