Schema (One)
Embeds a single Node schema block inline. Use it for optional or singular nested components such as a CTA, a banner, or an author card.
Embeds a single Node schema block inline within the parent document. Use it for optional or singular nested components — a call-to-action, a feature highlight, or an author card. For a list of blocks use Schemas.
Value shape
{
"_id": "abc123",
"_schema": "button",
"label": "Get started",
"url": "https://example.com"
}The _schema field contains the Node schema identifier. Use it to look up the registered component in your frontend.
Options
| Option | Description |
|---|---|
| Schema | The Node schema(s) editors can place in this field. Required — select at least one. |
| Name | Unique field name in the Schema. Appears in the generated model and in the API response. |
| Display Name | Label shown to editors in the Content Editor. |
| Required | When set, editors cannot save the document without a value. |
| Translatable | Not available for this field type. The fields inside the embedded schemas keep their own setting. |
| Description | Help text shown to editors under the field. |
| Default Value | Stored with the field definition. It is not currently pre-filled into new documents. |
References (Multiple)
Stores references to multiple content documents in the space. Resolved to full document objects when fetched with resolveReference enabled.
Schemas (Multiple)
Embeds a list of Node schema blocks inline. Use it for repeatable components such as page sections, button groups, or feature lists.