Skip to content
Content — Adapters

A visual field-mapping engine, not just a field renamer

An Adapter is a named, reusable mapping between two Contracts, built in a node canvas. Five real examples, start to finish: direct rules, crossing a list boundary, reading a structural value's fields, dispatching on a real type, and relaying a linked page's own Presentation through unchanged.

1

One engine: direct, computed, nested, and lookup rules

An Adapter is a named, reusable field mapping from one Contract to another — built once, in a visual canvas, and reused across every binding that needs it. The simplest rule kind is direct: connect one input field straight to one output field, like "Subpage to Nav Card" mapping Heading → Title.

Three more rule kinds handle everything a straight rename can't: computed builds a value from a small, deliberately tiny expression tree (concatenate, coalesce, cast, take-first — never a free-text formula language), nested maps an inner structural value through its own sub-Adapter, and lookup follows a reference to pull a value from the thing it points at.

The ebitex Content Adapter canvas for "Subpage to Nav Card": Input Contract Summary With Media, Output Contract Nav Card, with Heading connected to Title and Media connected to Thumbnail
2

Cross a list boundary with Foreach

None of those four rule kinds can turn one list into another — that needs its own node. For each item is the only node in the canvas that crosses a list boundary: point it at an enumerable input field, and its body — authored on its own drill-in canvas — runs once per item to produce one item of the output list.

Here, a Site Nav's Related Links (a list of Experience references) becomes a Cards list, one card per link, via a Foreach in "Map each item" mode.

The ebitex Content Adapter canvas for "Demo: Links to Nav Cards": a "Related Links" experienceReference list feeding a "For each item" Foreach node in Map each item mode, producing a "Cards" component list
3

Read a structural value's fields with Expand, and filter as you go

Inside that Foreach body, Expand fields is the node that reads a structural value's own fields — the only node with more than one output port, one per field the value actually has. Here it expands the linked page's own projection (Name, URL, Component, Presentation) so the body can pick which pieces become the card.

The body also carries a Keep item when port: an optional boolean predicate evaluated per item, before the rest of the body runs. Wire something to it and a mixed list — some links resolvable, some not — stops shipping hollow placeholder cards for the ones that fail.

The ebitex Content Adapter canvas showing a Foreach body: an "Item" experienceReference feeding "Expand fields" (Name, URL, Component, Presentation ports), plus a "Result" output and a "Keep item when" filter port
4

Dispatch on the real type with Switch on Contract, and plain logic with If/Equals/Exists

A reference or component field is often polymorphic — it can point at more than one kind of Contract. Switch on Contract dispatches on whichever Contract a value actually turns out to be: one narrowed output port per case, so a downstream Expand only ever sees the fields that case actually has.

Rounding out the canvas are three small, deliberately narrow logic nodes — If/else, Equals (strict-typed, no coercion), and Exists (true unless a value is missing or an empty string). No arithmetic, no string functions — just enough to drive a Keep-item-when filter or an If/else branch. Add on demand, not up front.

The ebitex Content Adapter canvas showing an "Exists" node ("True unless the value is missing or an empty string") feeding a "Keep item when" filter port, alongside an "Expand Linked Experience" node
5

Relay a linked page's own Presentation, unchanged

Sometimes the right "thumbnail" for a linked page isn't a title and an image pulled off its fields at all — it's whatever that page is already configured to render for itself: its own Template, bound Component, and settings. Expand Linked Experience's Presentation port relays that rendering through as-is, so a Featured Pages list can show each page exactly as its own author set it up, not a second-guessed re-derivation of it.

Here, a Navigation Group's links become a Featured Pages list of presentation-typed items — mapped, and filtered by the same Keep-item-when mechanism, so an external link (which has no Experience target to relay) is dropped rather than shipped as a blank card.

The ebitex Content Adapter canvas for "Navigation Group → Featured Pages": a Links field feeding a Foreach node producing a Featured field of type presentation, labeled "Mapped — produces a list of presentation. Filtered."
One engine, every environment

The same Adapter runs at authoring preview, publish, and delivery

There's exactly one server-side mapping engine — no separate client-side evaluator to keep in sync. A publish freezes an Adapter's rules into the snapshot it produced; editing a named Adapter later never changes already-published output until the next republish.