Experiences Reference Overview

This section contains reference documentation for Ligantic Experience schemas and block types.

Scope

Experience reference documentation covers:

• Experience content schema structure
• Block type schemas and per-block configuration
• Shared style/layout/data-binding properties used by blocks
• Block state configuration and availability

Entry Points

• Experience Blocks Reference
• Experience States and Print Layout

Datum Reference Date Formatting

When a datum reference points to a date field, the value is automatically formatted using the following cascade:

1. Reference-level format — optional date format set on the datum reference overrides the field default
2. Field-level defaultFormat — from the schema field's configuration
3. ISO fallback — raw string value if no format is configured

The timezoneDisplay setting on the Schema field controls whether dates are shown in the stored (source) timezone or converted to the viewer's timezone, including custom date patterns.

See Schema Field Types Reference — date for format preset and custom pattern details.

Datum Reference Number Formatting

When a datum reference points to a number field, the value is formatted in the viewer's locale using the following cascade:

1. Reference-level numberFormat — optional number format set on the datum reference overrides the field default
2. Field-level defaultFormat — from the schema field's configuration
3. Unformatted — the number as stored if no format is configured

See Schema Field Types Reference — number for format presets and custom options.

Dangling Datum References

A datum reference is dangling when the datum it points to no longer exists — for example, the block that provides it (such as a forEach) was deleted in the Experience designer after the reference was saved.

Dangling references do not stop the Experience from displaying:

• Published Experiences — the block renders its fallback (for example, fallbackText, or the variable node's defaultValue for variables in content) and the Experience remains viewable.
• Experience designer — the block renders the same fallback. The block is also surfaced with a needs setup overlay, the same treatment as unconfigured Button blocks and unconnected Input blocks: an orange dashed border is always shown, and the ⚙ Datum reference missing badge appears while the block (or anything inside it) is hovered on the canvas or in the Layers panel, or while it is selected.

Datums Bound to a Schema the Viewer Cannot Read

A block can bind a datum to a Schema that the viewer's Space Role cannot read — for example, a form whose entity context uses a Schema the Guest role has no access to. The viewer never receives that Schema's configuration or Records, and the Experience still displays:

• Input blocks bound to that Schema are not shown.
• Other content inside a block whose entity context uses that Schema, such as static text, is still shown when the page first appears, without any data from that Schema.
• Once the page has finished loading in the browser, a block whose entity context uses that Schema is hidden.

To show these blocks, grant the viewer's Space Role access to the Schema.